public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: discuss@x86-64.org, zippel@linux-m68k.org,
	linux-kernel@vger.kernel.org, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [discuss] Re: [1/3] Add 4GB DMA32 zone
Date: Tue, 13 Sep 2005 13:32:16 +0200	[thread overview]
Message-ID: <200509131332.17244.ak@suse.de> (raw)
In-Reply-To: <20050913031540.0c732284.akpm@osdl.org>


Hmm ok description is not very enlightening. 4 zones should indeed
still fit into 2 bits.

Kamezawa-san, can you please explain why exactly you did that change?

Thanks,
-Andi

On Tuesday 13 September 2005 12:15, Andrew Morton wrote:
> Andi Kleen <ak@suse.de> wrote:
> > Andrew do you still have the patch with
> >  the description? It must have been between 2.6.13mm1 and  2.6.13mm2.
>
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> Because 2.6.13-mm2  adds new zone DMA32, ZONES_SHIFT becomes 3.
> So, flags bits reserved for (SECTION | NODE | ZONE) should be increase.
>
> ZONE_SHIFT is increased, FLAGS_RESERVED should be.
>
> Signed-off-by Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Cc: Andi Kleen <ak@muc.de>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
>  include/linux/mmzone.h |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff -puN include/linux/mmzone.h~x86_64-dma32-fix include/linux/mmzone.h
> --- 25/include/linux/mmzone.h~x86_64-dma32-fix	Fri Sep  9 17:13:41 2005
> +++ 25-akpm/include/linux/mmzone.h	Fri Sep  9 17:14:13 2005
> @@ -431,9 +431,10 @@ extern struct pglist_data contig_page_da
>  #if BITS_PER_LONG == 32 || defined(ARCH_HAS_ATOMIC_UNSIGNED)
>  /*
>   * with 32 bit page->flags field, we reserve 8 bits for node/zone info.
> - * there are 3 zones (2 bits) and this leaves 8-2=6 bits for nodes.
> + * there are 4 zones (3 bits) and this leaves 8-2=6 bits for nodes.
> + * +6bits for sections if CONFIG_SPARSEMEM
>   */
> -#define FLAGS_RESERVED		8
> +#define FLAGS_RESERVED		9
>
>  #elif BITS_PER_LONG == 64
>  /*
> _

  reply	other threads:[~2005-09-13 11:32 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       ` [discuss] " Andi Kleen
2005-09-13 10:15         ` Andrew Morton
2005-09-13 11:32           ` Andi Kleen [this message]
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=200509131332.17244.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --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