http://bugzilla.suse.com/show_bug.cgi?id=1013629
http://bugzilla.suse.com/show_bug.cgi?id=1013629#c16
Vlastimil Babka
Of course kswapd was using 100% CPU, consequently a simple cp and `sleep 1` together would take 2 seconds to complete, which is why the vmstat file timestamps aren't consecutive.
You could try perf sampling to see where kswapd spends the cpu: perf record -a -g (let it run for e.g. a minute, then ctrl^c perf report -g
Should I disable THP and monitor for its occurrence?
-- You are receiving this mail because: You are on the CC list for the bug.