From: Andrew Morton <akpm@osdl.org>
To: colpatch@us.ibm.com
Cc: linux-kernel@vger.kernel.org, mbligh@aracnet.com, jbarnes@sgi.com
Subject: Re: [PATCH] Simplify node/zone field in page->flags
Date: Mon, 22 Dec 2003 13:11:26 -0800 [thread overview]
Message-ID: <20031222131126.66bef9a2.akpm@osdl.org> (raw)
In-Reply-To: <3FE74B43.7010407@us.ibm.com>
Matthew Dobson <colpatch@us.ibm.com> wrote:
>
> Currently we keep track of a pages node & zone in the top 8 bits (on
> 32-bit arches, 10 bits on 64-bit arches) of page->flags. We typically
> compute the field as follows:
> node_num * MAX_NR_ZONES + zone_num = 'nodezone'
>
> It's non-trivial to break this 'nodezone' back into node and zone
> numbers. This patch modifies the way we compute the index to be:
> (node_num << ZONE_SHIFT) | zone_num
>
> This makes it trivial to recover either the node or zone number with a
> simple bitshift. There are many places in the kernel where we do things
> like: page_zone(page)->zone_pgdat->node_id to determine the node a page
> belongs to. With this patch we save several pointer dereferences, and
> it all boils down to shifting some bits.
This conflicts with (is a superset of)
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm5/broken-out/ZONE_SHIFT-from-NODES_SHIFT.patch
I suspect you've sent a replacement patch, yes? If Jesse is OK with the
new patch I'll do the swap, thanks.
next prev parent reply other threads:[~2003-12-22 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 19:51 Matthew Dobson
2003-12-22 21:11 ` Andrew Morton [this message]
2004-01-05 21:22 ` Matthew Dobson
2004-01-05 21:37 ` Jesse Barnes
2004-01-05 22:31 ` Matthew Dobson
2004-01-05 22:33 ` Matthew Dobson
2004-01-05 23:23 ` Martin Schlemmer
2004-01-06 0:26 ` Matthew Dobson
2004-01-06 22:25 ` Matthew Dobson
2004-01-07 16:43 ` Martin Schlemmer
2004-03-29 15:45 ` Matthew Dobson
2004-03-29 15:45 ` Martin Schlemmer
2004-03-29 15:45 ` Matthew Dobson
2004-03-29 15:45 ` Matthew Dobson
2004-03-29 15:45 ` Jesse Barnes
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=20031222131126.66bef9a2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=jbarnes@sgi.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
Powered by JetHome