From: Adam Litke <agl@us.ibm.com>
To: linux-mm <linux-mm@kvack.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
nacc <nacc@linux.vnet.ibm.com>,
mel@csn.ul.ie, apw <apw@shadowen.org>,
agl <agl@linux.vnet.ibm.com>
Subject: [BUG] Make setup_zone_migrate_reserve() aware of overlapping nodes
Date: Wed, 20 Aug 2008 12:08:54 -0500 [thread overview]
Message-ID: <1219252134.13885.25.camel@localhost.localdomain> (raw)
In-Reply-To: <1218837685.12953.11.camel@localhost.localdomain>
I have gotten to the root cause of the hugetlb badness I reported back
on August 15th. My system has the following memory topology (note the
overlapping node):
i>>?Node 0 Memory: 0x8000000-0x44000000
i>>?Node 1 Memory: 0x0-0x8000000 0x44000000-0x80000000
setup_zone_migrate_reserve() scans the address range 0x0-0x8000000
looking for a pageblock to move onto the MIGRATE_RESERVE list. Finding
no candidates, it happily continues the scan into 0x8000000-0x44000000.
When a pageblock is found, the pages are moved to the MIGRATE_RESERVE
list on the wrong zone. Oops.
(Andrew: once the proper fix is agreed upon, this should also be a
candidate for -stable.)
setup_zone_migrate_reserve() should skip pageblocks in overlapping
nodes.
Signed-off-by: Adam Litke <agl@us.ibm.com>
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index af982f7..f297a9b 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -2512,6 +2512,10 @@ static void setup_zone_migrate_reserve(struct zone *zone)
pageblock_order;
for (pfn = start_pfn; pfn < end_pfn; pfn += pageblock_nr_pages) {
+ /* Watch out for overlapping nodes */
+ if (!early_pfn_in_nid(pfn, zone->node))
+ continue;
+
if (!pfn_valid(pfn))
continue;
page = pfn_to_page(pfn);
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-20 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 22:01 [BUG] __GFP_THISNODE is not always honored Adam Litke
2008-08-18 10:59 ` Mel Gorman
2008-08-18 18:16 ` Adam Litke
2008-08-18 19:57 ` Mel Gorman
2008-08-18 19:14 ` Christoph Lameter
2008-08-18 19:21 ` Christoph Lameter
2008-08-18 19:52 ` Mel Gorman
2008-08-20 17:08 ` Adam Litke [this message]
2008-08-20 18:11 ` [BUG] Make setup_zone_migrate_reserve() aware of overlapping nodes Dave Hansen
2008-08-20 19:55 ` [BUG] [PATCH v2] " Adam Litke
2008-08-21 11:33 ` Mel Gorman
2008-08-26 9:29 ` Andy Whitcroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1219252134.13885.25.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=agl@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nacc@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox