On Thu, 2007-09-27 at 23:50 -0700, Andrew Morton wrote: > What we _don't_ want to happen is for other processes which are writing to > other, non-dead devices to get collaterally blocked. We have patches which > might fix that queued for 2.6.24. Peter? Nasty problem, don't do that :-) But yeah, with per BDI dirty limits we get stuck at whatever ratio that NFS server/mount (?) has - which could be 100%. Other processes will then work almost synchronously against their BDIs but it should work. [ They will lower the NFS-BDI's ratio, but some fancy clipping code will limit the other BDIs their dirty limit to not exceed the total limit. And with all these NFS pages stuck, that will still be nothing. ]
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- References:
- Prev by Date: [PATCH] CPU HOTPLUG: Avoid hotadd when proper possible_map isn't specified.
- Next by Date: Re: [PATCH -mm1 1/2] fixing idr_find() locking
- Previous by thread: Re: A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?)
- Next by thread: Re: A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?)
- Index(es):
 |