Messages in this thread | | | Subject | Re: [PATCH 10/18] writeback: dirty position control - bdi reserve area | From | Peter Zijlstra <> | Date | Thu, 29 Sep 2011 10:49:57 +0200 |
| |
On Thu, 2011-09-29 at 11:32 +0800, Wu Fengguang wrote: > > Now I guess the only problem is when nr_bdi * MIN_WRITEBACK_PAGES ~ > > limit, at which point things go pear shaped. > > Yes. In that case the global @dirty will always be drove up to @limit. > Once @dirty dropped reasonably below, whichever bdi task wakeup first > will take the chance to fill the gap, which is not fair for bdi's of > different speed. > > Let me retry the thresh=1M,10M test cases without MIN_WRITEBACK_PAGES. > Hopefully the removal of it won't impact performance a lot.
Right, so alternatively we could try an argument that this is sufficiently rare and shouldn't happen. People with lots of disks tend to also have lots of memory, etc.
If we do find it happens we can always look at it again.
| |