All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	Linux Hotplug Memory Support  <lhms-devel@lists.sourceforge.net>
Subject: Re: [Patch/RFC]Removing zone and node ID from page->flags[0/3]
Date: Thu, 23 Sep 2004 16:27:13 -0700	[thread overview]
Message-ID: <20040923232713.GJ9106@holomorphy.com> (raw)
In-Reply-To: <20040923135108.D8CC.YGOTO@us.fujitsu.com>

On Thu, Sep 23, 2004 at 03:55:16PM -0700, Yasunori Goto wrote:
> I updated my patches which remove zone and node ID from page->flags.
> Page->flags is 32bit space and 19 bits of them have already been used on
> 2.6.9-rc2-mm2 kernel, and zone and node ID uses 8 bits on 32 archtecture.
> So, remaining bits is only 5 bits. In addition, only 3 bits have remained
> on 2.6.8.1 stock kernel.
> But, my patches make more 8 bits space in page->flags again.
> And kernel can use large number of node and types of zone.
> These patches are for 2.6.9-rc2-mm2. 

Looks relatively innocuous. I wonder if cosmetically we may want
s/struct zone_tbl/struct zone_table/

I like the path compression in the 2-level radix tree.

Thanks.


-- wli

WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Patch/RFC]Removing zone and node ID from page->flags[0/3]
Date: Thu, 23 Sep 2004 16:27:13 -0700	[thread overview]
Message-ID: <20040923232713.GJ9106@holomorphy.com> (raw)
In-Reply-To: <20040923135108.D8CC.YGOTO@us.fujitsu.com>

On Thu, Sep 23, 2004 at 03:55:16PM -0700, Yasunori Goto wrote:
> I updated my patches which remove zone and node ID from page->flags.
> Page->flags is 32bit space and 19 bits of them have already been used on
> 2.6.9-rc2-mm2 kernel, and zone and node ID uses 8 bits on 32 archtecture.
> So, remaining bits is only 5 bits. In addition, only 3 bits have remained
> on 2.6.8.1 stock kernel.
> But, my patches make more 8 bits space in page->flags again.
> And kernel can use large number of node and types of zone.
> These patches are for 2.6.9-rc2-mm2. 

Looks relatively innocuous. I wonder if cosmetically we may want
s/struct zone_tbl/struct zone_table/

I like the path compression in the 2-level radix tree.

Thanks.


-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2004-09-23 23:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 22:55 [Patch/RFC]Removing zone and node ID from page->flags[0/3] Yasunori Goto
2004-09-23 22:55 ` Yasunori Goto
2004-09-23 23:00 ` [Patch/RFC]Removing zone and node ID from page->flags[1/3] Yasunori Goto
2004-09-23 23:00   ` Yasunori Goto
2004-09-23 23:02 ` [Patch/RFC]Make second level zone_table[2/3] Yasunori Goto
2004-09-23 23:02   ` Yasunori Goto
2004-09-23 23:04 ` [Patch/RFC]Reduce second level zone_table[3/3] Yasunori Goto
2004-09-23 23:04   ` Yasunori Goto
2004-09-23 23:27 ` William Lee Irwin III [this message]
2004-09-23 23:27   ` [Patch/RFC]Removing zone and node ID from page->flags[0/3] William Lee Irwin III
2004-09-24  3:51   ` Yasunori Goto
2004-09-24  3:51     ` Yasunori Goto
2004-09-24  4:01     ` William Lee Irwin III
2004-09-24  4:01       ` William Lee Irwin III

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=20040923232713.GJ9106@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ygoto@us.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.