linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	wli@holomorphy.com, agl@us.ibm.com, linux-mm@kvack.org
Subject: Re: [PATCH 3/4] hugetlb: interleave dequeueing of huge pages
Date: Mon, 24 Sep 2007 16:29:22 -0700	[thread overview]
Message-ID: <20070924232922.GF26104@us.ibm.com> (raw)
In-Reply-To: <20070924232346.GE26104@us.ibm.com>

On 24.09.2007 [16:23:46 -0700], Nishanth Aravamudan wrote:
> On 14.09.2007 [16:33:00 -0400], Lee Schermerhorn wrote:
> > On Fri, 2007-09-14 at 13:16 -0700, Christoph Lameter wrote:
> > > On Fri, 14 Sep 2007, Lee Schermerhorn wrote:
> > > 
> > > > Yeah, I mistyped...  But, nid IS private to that function.  This is a
> > > > valid use of static.  But, perhaps it could use a comment to call
> > > > attention to it.
> > > 
> > > I think its best to move nis outside of the function and give it a longer 
> > > name that is distinctive from names we use for local variables. F.e.
> > > 
> > > last_allocated_node
> > > 
> > > ?
> > 
> > I do like to see variables' [and functions'] visibility kept within
> > the minimum necessary scope, and moving it outside of the function
> > violates this.  Nothing else in the source file needs it.  But, If
> > Nish agrees, I guess I don't feel that strongly about it.  I like the
> > suggested name, tho'
> 
> I've changed the name, but I don't see how moving the scope helps. I
> guess I could it make it globally static -- as opposed to local to the
> function -- and then it would be easier to dequeue based upon the
> global's value (something Lee asked for earlier). However, that would
> require locking to avoid races between two processes both echo'ing
> values into the sysctl? I guess it's not a serious race with the sanity
> check that Andrew has in there, it just means sometimes a node might get
> skipped in the interleaving...

err, not skipped, but allocated to twice. Then again, we already have a
comment to that effect now. So I'll go ahead and test this out.

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-09-24 23:29 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 ` [PATCH 2/4] hugetlb: fix pool allocation with empty nodes Nishanth Aravamudan
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 [this message]
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=20070924232922.GF26104@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=agl@us.ibm.com \
    --cc=clameter@sgi.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).