From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: anton@samba.org, akpm@linux-foundation.org,
lee.schermerhorn@hp.com, mel@csn.ul.ie, agl@us.ibm.com,
wli@holomorphy.com, linux-mm@kvack.org
Subject: Re: [PATCH] hugetlb: fix hugepage allocation with memoryless nodes
Date: Wed, 10 Oct 2007 21:29:48 -0700 [thread overview]
Message-ID: <20071011042948.GC32657@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710102112470.28507@schroedinger.engr.sgi.com>
On 10.10.2007 [21:14:48 -0700], Christoph Lameter wrote:
> On Wed, 10 Oct 2007, Nishanth Aravamudan wrote:
>
> > > +++ b/mm/hugetlb.c
> > > @@ -32,6 +32,7 @@ static unsigned int surplus_huge_pages_node[MAX_NUMNODES];
> > > static gfp_t htlb_alloc_mask = GFP_HIGHUSER;
> > > unsigned long hugepages_treat_as_movable;
> > > int hugetlb_dynamic_pool;
> > > +static int last_allocated_nid;
> >
> > While reworking patch 2/2 to incorporate the current state of hugetlb.c
> > after Adam's stack is applied, I realized that this is not a very good
> > name. It actually is the *current* nid to try to allocate hugepages on.
> >
> > Christoph, since you proposed the name, do you think
> >
> > hugetlb_current_nid
> >
> > is ok, too? If so I'll change the name throughout the patch (no
> > functional change).
>
> Sure. However, current is bit ambiguous. Is it the node we used last
> or the one to use next? Call it next_hugetlb_nid? Either way is fine
> with me though.
Good point. Given the way the code is laid out now, it always represents
the nid to allocate on next (so is the first one to try).
next_hugetlb_nid or hugetlb_next_nid it is.
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>
next prev parent reply other threads:[~2007-10-11 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 1:27 [PATCH] hugetlb: fix hugepage allocation with memoryless nodes Nishanth Aravamudan
2007-10-11 4:11 ` Nishanth Aravamudan
2007-10-11 4:14 ` Christoph Lameter
2007-10-11 4:29 ` Nishanth Aravamudan [this message]
2007-10-11 5:18 ` [PATCH][UPDATED] " Nishanth Aravamudan
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=20071011042948.GC32657@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=clameter@sgi.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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).