On Wed, Jun 05, 2013 at 05:10:31PM +0200, Andrea Arcangeli wrote: > Zone reclaim locked breaks zone_reclaim_mode=1. If more than one > thread allocates memory at the same time, it forces a premature > allocation into remote NUMA nodes even when there's plenty of clean > cache to reclaim in the local nodes. > > Signed-off-by: Andrea Arcangeli <aarcange@xxxxxxxxxx> Be aware that after this patch is applied that it is possible to have a situation like this 1. 4 processes running on node 1 2. Each process tries to allocate 30% of memory 3. Each process reads the full buffer in a loop (stupid, just an example) In this situation the processes will continually interfere with each other until one of them gets migrated to another zone by the scheduler. Watch for excessive reclaim, swapping and page writes from reclaim context as a result of this patch. A less stupid example is four file intensive workloads running in one node interfering with each other. Before this patch, one process would make forward progress and the others would fall back to using remote memory until all 4 processes had all the memory they need. At this point it is no longer allocating new pages or in reclaim. Most users will not notice additional remote accesses but I bet you they will notice swap/reclaim storms when there is plenty of memory on other nodes. Direct reclaim suffers a similar problem but to a much lesser extent. Users of direct reclaim will fall back to other zones in the zonelist and kswapd mitigates entry into direct reclaim in a number of cases. -- Mel Gorman SUSE Labs -- 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>