From: William Lee Irwin III <wli@holomorphy.com>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] GFP_ZONEMASK vs. MAX_NR_ZONES
Date: Mon, 17 Mar 2003 18:54:24 -0800 [thread overview]
Message-ID: <20030318025424.GV20188@holomorphy.com> (raw)
In-Reply-To: <3E767C04.3000604@us.ibm.com>
On Mon, Mar 17, 2003 at 05:53:08PM -0800, Matthew Dobson wrote:
> node_zonelists looks like it should really be declared of size
> MAX_NR_ZONES, not GFP_ZONEMASK. GFP_ZONEMASK is currently 15, making
> node_zonelists an array of 16 elements. The extra zonelists are all
> just duplicates of the *real* zonelists, namely the first 3 entries.
> Again, if anyone can explain to me why I'm wrong in my thinking, I'd
> love to know. There's certainly no way you could bitwise-and something
> with any combination of the GFP_DMA and GFP_HIGHMEM flags to refer to
> the 12th zonelist or some such! Or am I crazy?
No, you're not crazy, you're right:
#define __GFP_DMA 0x01
#define __GFP_HIGHMEM 0x02
/* Action modifiers - doesn't change the zoning */
#define __GFP_WAIT 0x10 /* Can wait and reschedule? */
#define __GFP_HIGH 0x20 /* Should access emergency pools? */
#define __GFP_IO 0x40 /* Can start physical IO? */
#define __GFP_FS 0x80 /* Can call down to low-level FS? */
#define __GFP_COLD 0x100 /* Cache-cold page required */
#define __GFP_NOWARN 0x200 /* Suppress page allocation failure warning */
bits 3-6 of gfp masks are totally unused.
-- wli
prev parent reply other threads:[~2003-03-18 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 1:53 [patch] GFP_ZONEMASK vs. MAX_NR_ZONES Matthew Dobson
2003-03-18 2:54 ` William Lee Irwin III [this message]
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=20030318025424.GV20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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