On Tue, Apr 26, 2011 at 02:05:12PM +0800, Dave Young wrote: > On Tue, Apr 26, 2011 at 1:55 PM, Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > > On Tue, Apr 26, 2011 at 01:49:25PM +0800, Dave Young wrote: > >> Hi, > >> > >> When memory pressure is high, readahead could cause oom killing. > >> IMHO we should stop readaheading under such circumstancesãIf it's true > >> how to fix it? > > > > Good question. Before OOM there will be readahead thrashings, which > > can be addressed by this patch: > > > > http://lkml.org/lkml/2010/2/2/229 > > Hi, I'm not clear about the patch, could be regard as below cases? > 1) readahead alloc fail due to low memory such as other large allocation > 2) readahead thrashing caused by itself When memory pressure goes up (not as much as allocation failures and OOM), the readahead pages may be reclaimed before they are read() accessed by the user space. At the time read() asks for the page, it will have to be read from disk _again_. This is called readahead thrashing. What the patch does is to automatically detect readahead thrashing and shrink the readahead size adaptively, which will the reduce memory consumption by readahead buffers. Thanks, Fengguang > > > > However there seems no much interest on that feature.. I can separate > > that out and resubmit it standalone if necessary. > > > > Thanks, > > Fengguang > > > > > > -- > Regards > dave -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>