On 12/03/2012 02:14 PM, Jiri Slaby wrote:

On 11/27/2012 09:48 PM, Johannes Weiner wrote:

quoted

I hope I included everybody that participated in the various threads
on kswapd getting stuck / exhibiting high CPU usage.  We were looking
at at least three root causes as far as I can see, so it's not really
clear who observed which problem.  Please correct me if the
reported-by, tested-by, bisected-by tags are incomplete.

Hi, I reported the problem for the first time but I got lost in the
patches flying around very early.

Whatever is in the current -next, works for me since -next was
resurrected after the 2 weeks gap last week...

Bah, I always need to write an email to reproduce that. It's back:
3.7.0-rc7-next-20121130

[<ffffffff810b132a>] __cond_resched+0x2a/0x40
[<ffffffff81133770>] shrink_slab+0x1c0/0x2d0
[<ffffffff8113668d>] kswapd+0x65d/0xb50
[<ffffffff810a37b0>] kthread+0xc0/0xd0
[<ffffffff816ba4dc>] ret_from_fork+0x7c/0xb0
[<ffffffffffffffff>] 0xffffffffffffffff

Going to apply this:
https://lkml.org/lkml/2012/12/3/407
and wait another 5 days to see the results...

thanks,
-- 
js
suse labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>