From: David Rientjes <rientjes@google.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-mm@kvack.org, linux-numa@vger.kernel.org,
akpm@linux-foundation.org, Mel Gorman <mel@csn.ul.ie>,
Nishanth Aravamudan <nacc@us.ibm.com>,
Adam Litke <agl@us.ibm.com>, Andy Whitcroft <apw@canonical.com>,
eric.whitney@hp.com
Subject: Re: [PATCH 2/5] hugetlb: add nodemask arg to huge page alloc, free and surplus adjust fcns
Date: Tue, 25 Aug 2009 14:59:11 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908251451100.770@chino.kir.corp.google.com> (raw)
In-Reply-To: <1251233374.16229.2.camel@useless.americas.hpqcorp.net>
On Tue, 25 Aug 2009, Lee Schermerhorn wrote:
> > > @@ -622,19 +622,29 @@ static struct page *alloc_fresh_huge_pag
> > > }
> > >
> > > /*
> > > - * common helper function for hstate_next_node_to_{alloc|free}.
> > > - * return next node in node_online_map, wrapping at end.
> > > + * common helper functions for hstate_next_node_to_{alloc|free}.
> > > + * We may have allocated or freed a huge pages based on a different
> > > + * nodes_allowed, previously, so h->next_node_to_{alloc|free} might
> > > + * be outside of *nodes_allowed. Ensure that we use the next
> > > + * allowed node for alloc or free.
> > > */
> > > -static int next_node_allowed(int nid)
> > > +static int next_node_allowed(int nid, nodemask_t *nodes_allowed)
> > > {
> > > - nid = next_node(nid, node_online_map);
> > > + nid = next_node(nid, *nodes_allowed);
> > > if (nid == MAX_NUMNODES)
> > > - nid = first_node(node_online_map);
> > > + nid = first_node(*nodes_allowed);
> > > VM_BUG_ON(nid >= MAX_NUMNODES);
> > >
> > > return nid;
> > > }
> > >
> > > +static int this_node_allowed(int nid, nodemask_t *nodes_allowed)
> > > +{
> > > + if (!node_isset(nid, *nodes_allowed))
> > > + nid = next_node_allowed(nid, nodes_allowed);
> > > + return nid;
> > > +}
> >
> > Awkward name considering this doesn't simply return true or false as
> > expected, it returns a nid.
>
> Well, it's not a predicate function so I wouldn't expect true or false
> return, but I can see how the trailing "allowed" can sound like we're
> asking the question "Is this node allowed?". Maybe,
> "get_this_node_allowed()" or "get_start_node_allowed" [we return the nid
> to "startnid"], ... Or, do you have a suggestion?
>
this_node_allowed() just seemed like a very similar name to
cpuset_zone_allowed() in the cpuset code, which does return true or false
depending on whether the zone is allowed by current's cpuset. As usual
with the mempolicy discussions, I come from a biased cpuset perspective :)
> >
> > > +
> > > /*
> > > * Use a helper variable to find the next node and then
> > > * copy it back to next_nid_to_alloc afterwards:
> > > @@ -642,28 +652,34 @@ static int next_node_allowed(int nid)
> > > * pass invalid nid MAX_NUMNODES to alloc_pages_exact_node.
> > > * But we don't need to use a spin_lock here: it really
> > > * doesn't matter if occasionally a racer chooses the
> > > - * same nid as we do. Move nid forward in the mask even
> > > - * if we just successfully allocated a hugepage so that
> > > - * the next caller gets hugepages on the next node.
> > > + * same nid as we do. Move nid forward in the mask whether
> > > + * or not we just successfully allocated a hugepage so that
> > > + * the next allocation addresses the next node.
> > > */
> > > -static int hstate_next_node_to_alloc(struct hstate *h)
> > > +static int hstate_next_node_to_alloc(struct hstate *h,
> > > + nodemask_t *nodes_allowed)
> > > {
> > > int nid, next_nid;
> > >
> > > - nid = h->next_nid_to_alloc;
> > > - next_nid = next_node_allowed(nid);
> > > + if (!nodes_allowed)
> > > + nodes_allowed = &node_online_map;
> > > +
> > > + nid = this_node_allowed(h->next_nid_to_alloc, nodes_allowed);
> > > +
> > > + next_nid = next_node_allowed(nid, nodes_allowed);
> > > h->next_nid_to_alloc = next_nid;
> > > +
> > > return nid;
> > > }
> >
> > Don't need next_nid.
>
> Well, the pre-existing comment block indicated that the use of the
> apparently spurious next_nid variable is necessary to close a race. Not
> sure whether that comment still applies with this rework. What do you
> think?
>
What race is it closing exactly if gcc is going to optimize it out
anyways? I think you can safely fold the following into your patch.
---
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -659,15 +659,14 @@ static int this_node_allowed(int nid, nodemask_t *nodes_allowed)
static int hstate_next_node_to_alloc(struct hstate *h,
nodemask_t *nodes_allowed)
{
- int nid, next_nid;
+ int nid;
if (!nodes_allowed)
nodes_allowed = &node_online_map;
nid = this_node_allowed(h->next_nid_to_alloc, nodes_allowed);
- next_nid = next_node_allowed(nid, nodes_allowed);
- h->next_nid_to_alloc = next_nid;
+ h->next_nid_to_alloc = next_node_allowed(nid, nodes_allowed);
return nid;
}
@@ -707,15 +706,14 @@ static int alloc_fresh_huge_page(struct hstate *h, nodemask_t *nodes_allowed)
*/
static int hstate_next_node_to_free(struct hstate *h, nodemask_t *nodes_allowed)
{
- int nid, next_nid;
+ int nid;
if (!nodes_allowed)
nodes_allowed = &node_online_map;
nid = this_node_allowed(h->next_nid_to_free, nodes_allowed);
- next_nid = next_node_allowed(nid, nodes_allowed);
- h->next_nid_to_free = next_nid;
+ h->next_nid_to_free = next_node_allowed(nid, nodes_allowed);
return 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:[~2009-08-25 21:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 19:24 [PATCH 0/5] hugetlb: numa control of persistent huge pages alloc/free Lee Schermerhorn
2009-08-24 19:25 ` [PATCH 1/5] hugetlb: rework hstate_next_node_* functions Lee Schermerhorn
2009-08-25 8:10 ` David Rientjes
2009-08-24 19:26 ` [PATCH 2/5] hugetlb: add nodemask arg to huge page alloc, free and surplus adjust fcns Lee Schermerhorn
2009-08-25 8:16 ` David Rientjes
2009-08-25 20:49 ` Lee Schermerhorn
2009-08-25 21:59 ` David Rientjes [this message]
2009-08-26 9:58 ` Mel Gorman
2009-08-24 19:27 ` [PATCH 3/5] hugetlb: derive huge pages nodes allowed from task mempolicy Lee Schermerhorn
2009-08-25 8:47 ` David Rientjes
2009-08-25 20:49 ` Lee Schermerhorn
2009-08-27 19:40 ` David Rientjes
2009-08-25 10:22 ` Mel Gorman
2009-08-24 19:29 ` [PATCH 4/5] hugetlb: add per node hstate attributes Lee Schermerhorn
2009-08-25 10:19 ` Mel Gorman
2009-08-25 20:49 ` Lee Schermerhorn
2009-08-26 10:11 ` Mel Gorman
2009-08-26 18:02 ` Lee Schermerhorn
2009-08-26 19:47 ` David Rientjes
2009-08-26 20:46 ` Lee Schermerhorn
2009-08-27 9:52 ` Mel Gorman
2009-08-27 19:35 ` David Rientjes
2009-08-28 12:56 ` Lee Schermerhorn
2009-08-26 18:04 ` Lee Schermerhorn
2009-08-27 10:23 ` Mel Gorman
2009-08-27 16:52 ` Lee Schermerhorn
2009-08-28 10:09 ` Mel Gorman
2009-08-25 13:35 ` Mel Gorman
2009-08-25 20:49 ` Lee Schermerhorn
2009-08-26 10:12 ` Mel Gorman
2009-08-24 19:30 ` [PATCH 5/5] hugetlb: update hugetlb documentation for mempolicy based management Lee Schermerhorn
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=alpine.DEB.2.00.0908251451100.770@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=eric.whitney@hp.com \
--cc=linux-mm@kvack.org \
--cc=linux-numa@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.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