On Sun, Jun 19, 2011 at 11:01:11PM +0800, Wu Fengguang wrote: > The start of a heavy weight application (ie. KVM) may instantly knock > down determine_dirtyable_memory() and hence the global/bdi dirty > thresholds. > > So introduce global_dirty_limit for tracking the global dirty threshold > with policies > > - follow downwards slowly > - follow up in one shot > > global_dirty_limit can effectively mask out the impact of sudden drop of > dirtyable memory. It will be used in the next patch for two new type of > dirty limits. This needs to be explained in more detail in comments near the actual code. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
