From: Nishanth Aravamudan <nacc@us.ibm.com>
To: clameter@sgi.com
Cc: anton@samba.org, wli@holomorphy.com, agl@us.ibm.com,
lee.schermerhorn@hp.com, linux-mm@kvack.org
Subject: [PATCH 2/4] hugetlb: fix pool allocation with empty nodes
Date: Thu, 6 Sep 2007 11:24:30 -0700 [thread overview]
Message-ID: <20070906182430.GB7779@us.ibm.com> (raw)
In-Reply-To: <20070906182134.GA7779@us.ibm.com>
Anton found a problem with the hugetlb pool allocation when some nodes
have no memory (http://marc.info/?l=linux-mm&m=118133042025995&w=2). Lee
worked on versions that tried to fix it, but none were accepted.
Christoph has created a set of patches which allow for GFP_THISNODE
allocations to fail if the node has no memory and for exporting a
nodemask indicating which nodes have memory. Simply interleave across
this nodemask rather than the online nodemask.
Tested on 4-node ppc64, 2-node ia64 and 4-node x86_64.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
---
My 4-node ppc64 box with memoryless nodes is having issues with
2.6.23-rc4-mm1, so I'm unable to test. Lee, could you give this a spin?
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index edb2100..cc875c6 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -129,7 +129,7 @@ static int alloc_fresh_huge_page(void)
int ret = 0;
if (nid < 0)
- nid = first_node(node_online_map);
+ nid = first_node(node_states[N_HIGH_MEMORY]);
start_nid = nid;
do {
@@ -147,9 +147,9 @@ static int alloc_fresh_huge_page(void)
* successfully allocated a hugepage so that the next
* caller gets hugepages on the next node.
*/
- next_nid = next_node(nid, node_online_map);
+ next_nid = next_node(nid, node_states[N_HIGH_MEMORY]);
if (next_nid == MAX_NUMNODES)
- next_nid = first_node(node_online_map);
+ next_nid = first_node(node_states[N_HIGH_MEMORY]);
nid = next_nid;
} while (!page && nid != start_nid);
--
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:[~2007-09-06 18:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 18:21 [PATCH 1/4] hugetlb: search harder for memory in alloc_fresh_huge_page() Nishanth Aravamudan
2007-09-06 18:24 ` Nishanth Aravamudan [this message]
2007-09-06 18:27 ` [PATCH 3/4] hugetlb: interleave dequeueing of huge pages Nishanth Aravamudan
2007-09-06 18:28 ` [PATCH 4/4] hugetlb: add per-node nr_hugepages sysfs attribute Nishanth Aravamudan
2007-09-14 18:56 ` Christoph Lameter
2007-09-14 18:54 ` [PATCH 3/4] hugetlb: interleave dequeueing of huge pages Christoph Lameter
2007-09-14 19:03 ` Lee Schermerhorn
2007-09-14 19:42 ` Christoph Lameter
2007-09-14 20:09 ` Lee Schermerhorn
2007-09-14 20:16 ` Christoph Lameter
2007-09-14 20:33 ` Lee Schermerhorn
2007-09-24 23:23 ` Nishanth Aravamudan
2007-09-24 23:29 ` Nishanth Aravamudan
2007-09-14 18:53 ` [PATCH 2/4] hugetlb: fix pool allocation with empty nodes Christoph Lameter
2007-09-14 18:57 ` Christoph Lameter
2007-10-02 22:47 ` Nishanth Aravamudan
2007-10-02 23:39 ` Christoph Lameter
2007-09-14 17:26 ` [PATCH 1/4] hugetlb: search harder for memory in alloc_fresh_huge_page() Nishanth Aravamudan
2007-09-14 17:43 ` Christoph Lameter
2007-09-14 18:20 ` Lee Schermerhorn
2007-09-24 16:22 ` Nishanth Aravamudan
2007-09-24 19:07 ` Christoph Lameter
2007-09-14 18:51 ` Christoph Lameter
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=20070906182430.GB7779@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=agl@us.ibm.com \
--cc=anton@samba.org \
--cc=clameter@sgi.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).