On Tue, Dec 04, 2012 at 10:05:29AM +0100, Zdenek Kabelac wrote: > Dne 3.12.2012 20:18, Johannes Weiner napsal(a): > >Szia Zdenek, > > > >On Mon, Dec 03, 2012 at 04:23:15PM +0100, Zdenek Kabelac wrote: > >>Ok, bad news - I've been hit by kswapd0 loop again - > >>my kernel git commit cc19528bd3084c3c2d870b31a3578da8c69952f3 again > >>shown kswapd0 for couple minutes on CPU. > >> > >>It seemed to go instantly away when I've drop caches > >>(echo 3 >/proc/sys/vm/drop_cache) > >>(After that I've had over 1G free memory) > > > >Any chance you could retry with this patch on top? > > > >--- > >From: Johannes Weiner <hannes@xxxxxxxxxxx> > >Subject: [patch] mm: vmscan: do not keep kswapd looping forever due > > to individual uncompactable zones > > > >--- > > mm/vmscan.c | 16 ---------------- > > 1 file changed, 16 deletions(-) > > > >diff --git a/mm/vmscan.c b/mm/vmscan.c > > > Ok, I'm running now b69f0859dc8e633c5d8c06845811588fe17e68b3 (-rc8) > with your patch. I'll be able to give some feedback after couple > days (if I keep my machine running without reboot - since before > I had occasional problems with ACPI now resolved. > (https://bugzilla.kernel.org/show_bug.cgi?id=51071) > (patch not yet in -rc8) > I'm also using this extra patch: https://patchwork.kernel.org/patch/1792531/ Okay, fingers crossed! Thanks for persisting. > What seems to be triggering condition on my machine - running laptop > for some days - and having Thunderbird reaching 0.8G (I guess they > must keep all my news messages in memory to consume that size) and > Firefox 1.3GB of consumed > memory (assuming massive leaking with combination of flash) Were you able speed this process up in the past? I.e. by doing a search over all mail? Watching 8 nyan cat videos in parallel? If not, it's probably better not to change anything now... Thanks! -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>