linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: akpm@osdl.org, linux-mm@kvack.org,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	ak@suse.de
Subject: Re: linearly index zone->node_zonelists[]
Date: Tue, 8 Aug 2006 08:50:23 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608080847150.27273@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <44D8818F.3080703@shadowen.org>

On Tue, 8 Aug 2006, Andy Whitcroft wrote:

> The GFP_foo flags are modifiers specifying some property we require from an
> allocation.  Currently all modifiers are singletons, that is they are all
> specified in isolation.  However, the code base as it stands does not enforce
> this.  I could see use cases where we might want to specify more than one
> flag.  For example a GFP_NODE_LOCAL flags which could be specified with any of
> the 'zone selectors'.  This would naturally work with the current
> implementation.

I have a patch here that implements such a thing its called 
__GFP_THISNODE but it does not use any of the bit mask features that I 
removed. __GFP_THISNODE simply checks if the allocation zone is local.

> Making the change you suggest here codifies the singleton status of these
> bits.  We should be sure we are not going to use this feature before its
> removed.  I am not sure I am comfortable saying there are no uses for it.

This certainly codifies the singleton status. However, I cannot imagine 
any uses for it that would not also require other significant changes in 
the page allocator. We can revisit that if someone comes up with a feature 
that needs this.

--
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:[~2006-08-08 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 23:54 mempolicies: fix policy_zone check Christoph Lameter
2006-08-04 23:55 ` Apply type enum zone_type Christoph Lameter
2006-08-04 23:57   ` linearly index zone->node_zonelists[] Christoph Lameter
2006-08-05  1:50     ` Andi Kleen
2006-08-08 12:20     ` Andy Whitcroft
2006-08-08 15:50       ` Christoph Lameter [this message]
2006-08-05  1:38   ` Apply type enum zone_type Andi Kleen
2006-08-05  2:01     ` Christoph Lameter
2006-08-05  0:08 ` mempolicies: fix policy_zone check Andrew Morton
2006-08-05  0:18   ` Christoph Lameter
2006-08-07 13:40     ` Lee Schermerhorn
2006-08-05  1:49 ` Andi Kleen
2006-08-05  2:05   ` Christoph Lameter
2006-08-08 12:00 ` Andy Whitcroft

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.0608080847150.27273@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-mm@kvack.org \
    /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