On 03/04/2015 03:03 PM, Shaohua Li wrote: > kswapd is a per-node based. Sometimes there is imbalance between nodes, > node A is full of clean file pages (easy to reclaim), node B is > full of anon pages (hard to reclaim). With memory pressure, kswapd will > be waken up for both nodes. The kswapd of node B will try to swap, while > we prefer reclaim pages from node A first. The real issue here is we > don't have a mechanism to prevent memory allocation from a hard-reclaim > node (node B here) if there is an easy-reclaim node (node A) to reclaim > memory. > > The swap can happen even with swapiness 0. Below is a simple script to > trigger it. cpu 1 and 8 are in different node, each has 72G memory: > truncate -s 70G img > taskset -c 8 dd if=img of=/dev/null bs=4k > taskset -c 1 usemem 70G > > The swap can even easier to trigger because we have a protect mechanism > for situation file pages are less than high watermark. This logic makes > sense but could be more conservative. > > This patch doesn't try to fix the kswapd imbalance issue above, but make > get_scan_count more conservative to select anon pages. The protect > mechanism is designed for situation file pages are rotated frequently. > In that situation, page reclaim should be in trouble, eg, priority is > lower. So let's only apply the protect mechanism in that situation. In > pratice, this fixes the swap issue in above test. > > Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: Mel Gorman <mgorman@xxxxxxx> > Cc: Rik van Riel <riel@xxxxxxxxxx> > Cc: Johannes Weiner <hannes@xxxxxxxxxxx> > Signed-off-by: Shaohua Li <shli@xxxxxx> Doh, never mind my earlier comment. I must be too tired to look at stuff right... I see how your patch helps avoid the problem, but I am worried about potential side effects. I suspect it could lead to page cache thrashing when all zones are low on page cache memory. Would it make sense to explicitly check that we are low on page cache pages in all zones on the scan list, before forcing anon only scanning, when we get into this function? -- 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>