linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
	Lee.Schermerhorn@hp.com, ak@suse.de, anton@samba.org,
	mel@csn.ul.ie, akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] gfp.h: GFP_THISNODE can go to other nodes if some are unpopulated
Date: Mon, 11 Jun 2007 11:54:36 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706111153170.18684@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070611184656.GA9920@us.ibm.com>

On Mon, 11 Jun 2007, Nishanth Aravamudan wrote:

> > +	do {
> > +		next = next_node(nid, policy->v.nodes);
> > +		if (next >= MAX_NUMNODES)
> > +			next = first_node(policy->v.nodes);
> > +	} while (!NODE_DATA(node)->present_pages);
> 
> If something like Lee/Anton's patch were to go in (which, as Lee pointed
> out, I refreshed as Patch 1/3 in the series I posted a few days ago),
> this would be
> 
> 	while(!node_populated(nid))

Right. That would be much better.

> Presuming I understand everything correctly. Not sure which would be
> preferred, or if perhaps node_populated, rather than using a nodemask
> should just use NODE_DATA(nid)->present_pages?

I think the node_populate is better. Simple bitmap lookup.


--
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-06-11 18:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 15:04 [PATCH] " Nishanth Aravamudan
2007-06-07 18:11 ` Christoph Lameter
2007-06-07 22:01   ` [PATCH v2] " Nishanth Aravamudan
2007-06-07 22:05     ` Christoph Lameter
2007-06-07 22:16       ` Nishanth Aravamudan
2007-06-11 12:49     ` Andy Whitcroft
2007-06-11 16:12       ` Christoph Lameter
2007-06-11 16:42         ` Christoph Lameter
2007-06-11 17:12           ` Nishanth Aravamudan
2007-06-11 18:29             ` Christoph Lameter
2007-06-11 18:46               ` Nishanth Aravamudan
2007-06-11 18:54                 ` Christoph Lameter [this message]
2007-06-11 19:36               ` Nishanth Aravamudan
2007-06-11 19:43                 ` Christoph Lameter
2007-06-11 20:18                   ` Nishanth Aravamudan
2007-06-11 18:23           ` Lee Schermerhorn
2007-06-11 18:40             ` 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=Pine.LNX.4.64.0706111153170.18684@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=apw@shadowen.org \
    --cc=linux-mm@kvack.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