linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: [Patch:000/005] wait_table and zonelist initializing for memory hotadd
Date: Tue, 11 Apr 2006 20:25:22 +0900	[thread overview]
Message-ID: <20060411202031.5643.Y-GOTO@jp.fujitsu.com> (raw)

Hi.

These are patches for initialization of wait_table and updating of zonelists
for memory hot-add.
These patches can be used when a new node/zone becomes available.
When empty zone becomes not empty by memory hot-add, 
wait_table must be initialized, and zonelists must be updated.

  ex) x86-64 is good example of new zone addition.
      - System boot up with memory under 4G address.
        All of memory will be ZONE_DMA32.
      - Then hot-add over 4G memory. It becomes ZONE_NORMAL. But, 
        wait table of zone normal is not initialized at this time.

This patch is for 2.6.17-rc1-mm2.

Please apply.

----------------------------
Change log from v1 of wait_table init and build_zonelist.
  - update for 2.6.17-rc1-mm2.
  - add comment for wait_table hash entries.
  - change name wait_table_size() -> wait_table_hash_nr_entries()

Change log from v4 of node hot-add.
  - wait_table and build_zonelists updating are picked up.
  - update for 2.6.17-rc1-mm1.
  - change allocation for wait_table from kmalloc() to vmalloc().
    vmalloc() is enough for it.

V4 of post is here.
<description>
http://marc.theaimsgroup.com/?l=linux-mm&w=2&r=1&s=memory+hotplug+node+v.4&q=b
<patches>
http://marc.theaimsgroup.com/?l=linux-mm&w=2&r=1&s=memory+hotplug+node+v.4.&q=b



-- 
Yasunori Goto 


--
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:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2006-04-11 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 11:25 Yasunori Goto [this message]
2006-04-11 11:30 ` [Patch:001/005] wait_table and zonelist initializing for memory hotadd (change name of wait_table_size()) Yasunori Goto
2006-04-11 11:30 ` [Patch:002/005] wait_table and zonelist initializing for memory hotadd (change to meminit for build_zonelist) Yasunori Goto
2006-04-11 11:30 ` [Patch:003/005] wait_table and zonelist initializing for memory hotadd(add return code for init_current_empty_zone) Yasunori Goto
2006-04-11 11:30 ` [Patch:004/005] wait_table and zonelist initializing for memory hotadd (wait_table initialization) Yasunori Goto
2006-04-11 11:30 ` [Patch:005/005] wait_table and zonelist initializing for memory hotadd (update zonelists) Yasunori Goto

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=20060411202031.5643.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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