The patch titled
page allocator: sort node map earlier
has been removed from the -mm tree. Its filename was
page-allocator-sort-node-map-earlier.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: page allocator: sort node map earlier
From: mel@xxxxxxxxx (Mel Gorman)
find_min_pfn_for_node() and find_min_pfn_with_active_regions() both depend
on a sorted early_node_map[]. However, sort_node_map() is being called
after fin_min_pfn_with_active_regions() in free_area_init_nodes(). In most
cases, this is ok, but on at least one x86_64, the SRAT table caused the
E820 ranges to be registered out of order. This gave the wrong values for
the min PFN range resulting in some pages not being initialised.
This patch sorts the early_node_map in find_min_pfn_for_node(). It has
been boot tested on x86, x86_64, ppc64 and ia64.
Signed-off-by: Mel Gorman <mel@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
mm/page_alloc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -puN mm/page_alloc.c~page-allocator-sort-node-map-earlier mm/page_alloc.c
--- a/mm/page_alloc.c~page-allocator-sort-node-map-earlier
+++ a/mm/page_alloc.c
@@ -2612,6 +2612,9 @@ unsigned long __init find_min_pfn_for_no
{
int i;
+ /* Regions in the early_node_map can be in any order */
+ sort_node_map();
+
/* Assuming a sorted map, the first range found has the starting pfn */
for_each_active_range_index_in_nid(i, nid)
return early_node_map[i].start_pfn;
@@ -2680,9 +2683,6 @@ void __init free_area_init_nodes(unsigne
max(max_zone_pfn[i], arch_zone_lowest_possible_pfn[i]);
}
- /* Regions in the early_node_map can be in any order */
- sort_node_map();
-
/* Print out the zone ranges */
printk("Zone PFN ranges:\n");
for (i = 0; i < MAX_NR_ZONES; i++)
_
Patches currently in -mm which might be from mel@xxxxxxxxx are
origin.patch
ext2-reservations.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
