linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: clameter@sgi.com
Cc: wli@holomorphy.com, anton@samba.org, agl@us.ibm.com,
	lee.schermerhorn@hp.com, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] hugetlb: fix pool allocation with empty nodes
Date: Wed, 3 Oct 2007 20:12:29 -0700	[thread overview]
Message-ID: <20071004031229.GE29663@us.ibm.com> (raw)
In-Reply-To: <20071003224904.GC29663@us.ibm.com>

On 03.10.2007 [15:49:04 -0700], Nishanth Aravamudan wrote:
> hugetlb: fix pool allocation with empty nodes
> 
> 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 x86 !NUMA, x86 NUMA, x86_64 NUMA, ppc64 NUMA with 2 memoryless
> nodes.
> 
> Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> 
> ---
> Would it be better to combine this patch directly in 1/2? There is no
> functional difference, really, just a matter of 'correctness'. Without
> this patch, we'll iterate over nodes that we can't possibly do THISNODE
> allocations on. So I guess this falls more into an optimization?
> 
> Also, I see that Adam's patches have been pulled in for the next -mm. I
> can rebase on top of them and retest to minimise Andrew's work.

FWIW, both patches apply pretty easily on top of Adam's stack. 1/2
requires a bit of massaging because functions have moved out of their
context, but 2/2 applies cleanly. I noticed, though, that Adam's patches
use node_online_map when they should use node_states[N_HIGH_MEMORY], so
shall I modify this patch to simply be

hugetlb: only iterate over populated nodes

and fix all of the instances in hugetlb.c?

Still need to test the patches on top of Adam's stack before I'll ask
Andrew to pick them up.

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@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>

  reply	other threads:[~2007-10-04  3:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 22:45 [PATCH 1/2] hugetlb: search harder for memory in alloc_fresh_huge_page() Nishanth Aravamudan
2007-10-03 22:49 ` [PATCH 2/2] hugetlb: fix pool allocation with empty nodes Nishanth Aravamudan
2007-10-04  3:12   ` Nishanth Aravamudan [this message]
2007-10-05 19:56     ` Lee Schermerhorn
2007-10-05 20:30       ` Nishanth Aravamudan
2007-10-04  3:55   ` Christoph Lameter
2007-10-08 17:39     ` Nishanth Aravamudan
2007-10-04  3:54 ` [PATCH 1/2] hugetlb: search harder for memory in alloc_fresh_huge_page() 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=20071004031229.GE29663@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).