From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [discuss] Re: [1/3] Add 4GB DMA32 zone
Date: Tue, 13 Sep 2005 11:47:41 +0200 [thread overview]
Message-ID: <200509131147.42140.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0509131107360.3728@scrub.home>
On Tuesday 13 September 2005 11:15, Roman Zippel wrote:
> Hi,
>
> On Mon, 12 Sep 2005, Andi Kleen wrote:
> > > On Sun, 11 Sep 2005, Andi Kleen wrote:
> > > > -#define MAX_NR_ZONES 3 /* Sync this with ZONES_SHIFT */
> > > > -#define ZONES_SHIFT 2 /* ceil(log2(MAX_NR_ZONES)) */
> > > > +#define MAX_NR_ZONES 4 /* Sync this with ZONES_SHIFT */
> > > > +#define ZONES_SHIFT 3 /* ceil(log2(MAX_NR_ZONES)) */
> > >
> > > Why needs ZONES_SHIFT to be increased?
> > >
> > > > -#define FLAGS_RESERVED 8
> > > > +#define FLAGS_RESERVED 9
> > >
> > > I would prefer to keep this at 8.
> >
> > sparsemem needs these two.
>
> Did I somehow offend you, that I don't deserve an answer?
Well, your aggressive tone definitely doesn't encourage speedy answers.
> The reason for my question is rather simple (and I thought obvious), the
> four zone types fit into two bits, so what is sparsemem doing with this
> extra bit?
iirc it was a patch that came in over Andrew. I can't find the email anymore
unfortunately. The argument looked plausible and I think it fixed
a boot problem for the submitter on some arch (probably IA64, on x86-64 it
worked fine without it, but I've never tried sparsemem and the code was
originally written before sparsemem). Andrew do you still have the patch with
the description? It must have been between 2.6.13mm1 and 2.6.13mm2.
You're right that four zones should in theory fit into 2 bits, so I'm
also not sure why it was needed.
-Andi
next prev parent reply other threads:[~2005-09-13 9:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:59 [1/3] Add 4GB DMA32 zone Andi Kleen
2005-09-12 7:44 ` [discuss] " Jan Beulich
2005-09-12 7:58 ` Andi Kleen
2005-09-12 10:28 ` Alan Cox
2005-09-12 10:42 ` Andi Kleen
2005-09-12 11:33 ` Alan Cox
2005-09-12 11:22 ` Andi Kleen
2005-09-12 12:34 ` Alan Cox
2005-09-12 12:28 ` [discuss] " Andi Kleen
2005-09-12 18:18 ` Jeff Garzik
2005-09-12 22:02 ` Bart Hartgers
2005-09-13 3:20 ` Andi Kleen
2005-09-12 19:55 ` Mark Lord
2005-09-12 12:45 ` Roman Zippel
2005-09-12 12:46 ` Andi Kleen
2005-09-12 12:50 ` Roman Zippel
2005-09-12 12:54 ` Andi Kleen
2005-09-12 13:01 ` Roman Zippel
2005-09-13 9:15 ` Roman Zippel
2005-09-13 9:47 ` Andi Kleen [this message]
2005-09-13 10:15 ` [discuss] " Andrew Morton
2005-09-13 11:32 ` Andi Kleen
2005-09-13 12:09 ` Roman Zippel
2005-09-13 23:51 ` KAMEZAWA Hiroyuki
2005-10-03 15:46 ` Coywolf Qi Hunt
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=200509131147.42140.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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