From: jbarnes@sgi.com (Jesse Barnes)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use NODES_SHIFT to calculate ZONE_SHIFT
Date: Fri, 7 Nov 2003 14:01:50 -0800 [thread overview]
Message-ID: <20031107220150.GA1799@sgi.com> (raw)
In-Reply-To: <20031107135806.3c929688.akpm@osdl.org>
On Fri, Nov 07, 2003 at 01:58:06PM -0800, Andrew Morton wrote:
> jbarnes@sgi.com (Jesse Barnes) wrote:
> >
> > Now that we have a proper NODES_SHIFT value, we need to use it to define
> > ZONE_SHIFT otherwise we'll spill over 8 bits if we have more than 85
> > nodes. How does this look? The '+2' should really be
> > log2(MAX_NR_NODES), but I think this is an improvement over what was
> > there.
>
> You mean log2(MAX_NR_ZONES).
Yep, sorry.
> How about we do it this way, so at least the duplicated information is on
> adjacent lines, and they are unlikely to get out of sync?
Yeah, this looks great.
Thanks,
Jesse
prev parent reply other threads:[~2003-11-07 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 21:16 [PATCH] use NODES_SHIFT to calculate ZONE_SHIFT Jesse Barnes
2003-11-07 21:58 ` Andrew Morton
2003-11-07 22:01 ` Jesse Barnes [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=20031107220150.GA1799@sgi.com \
--to=jbarnes@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).