Subject: [merged] mm-page_alloc-fix-doc-for-numa_zonelist_order.patch removed from -mm tree To: liwanp@xxxxxxxxxxxxxxxxxx,mhocko@xxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Tue, 09 Jul 2013 16:20:11 -0700 The patch titled Subject: mm/page_alloc: fix doc for numa_zonelist_order has been removed from the -mm tree. Its filename was mm-page_alloc-fix-doc-for-numa_zonelist_order.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Wanpeng Li <liwanp@xxxxxxxxxxxxxxxxxx> Subject: mm/page_alloc: fix doc for numa_zonelist_order The default zonelist order selecter will select "node" order if any node's DMA zone comprises greater than 70% of its local memory instead of 60%, according to default_zonelist_order::low_kmem_size > total * 70/100. Signed-off-by: Wanpeng Li <liwanp@xxxxxxxxxxxxxxxxxx> Reviewed-by: Michal Hocko <mhocko@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/sysctl/vm.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN Documentation/sysctl/vm.txt~mm-page_alloc-fix-doc-for-numa_zonelist_order Documentation/sysctl/vm.txt --- a/Documentation/sysctl/vm.txt~mm-page_alloc-fix-doc-for-numa_zonelist_order +++ a/Documentation/sysctl/vm.txt @@ -510,7 +510,7 @@ Specify "[Dd]efault" to request automati will select "node" order in following case. (1) if the DMA zone does not exist or (2) if the DMA zone comprises greater than 50% of the available memory or -(3) if any node's DMA zone comprises greater than 60% of its local memory and +(3) if any node's DMA zone comprises greater than 70% of its local memory and the amount of local memory is big enough. Otherwise, "zone" order will be selected. Default order is recommended unless _ Patches currently in -mm which might be from liwanp@xxxxxxxxxxxxxxxxxx are origin.patch linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html