From: tgh <tianguanhua@ncic.ac.cn>
To: linux-hotplug@vger.kernel.org
Subject: question about memory-hotplug
Date: Tue, 03 Apr 2007 02:43:25 +0000 [thread overview]
Message-ID: <4611BF4D.6020002@ncic.ac.cn> (raw)
hi
I try to understand the memory_hotplug.c ,but I am confused about
the mechanism in it
Does the mem_map is allocated when setup for all the memory page both
the existing and the hotplug , or does the mem_map is allocated
dynamically when a chip of memory is hotpluged ?
if mem_map is allocated dynamically,does the mem_map is maintained in
the list or how to deal with it ?
and if mem_map is allocated dynamically,does system need new node and
new zone structure to manage the dynamically-allocated memmap ,or not ?
if system need new node and new zone structure to manage the
dynamically-allocated memmap,does system have to be a NUMA-surpport one
or not?
I am confused about it
could you help me
Thanks in advance
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-04-03 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 2:43 tgh [this message]
2007-04-04 5:58 ` question about memory-hotplug Yasunori Goto
2007-04-04 8:53 ` tgh
2007-04-04 10:29 ` Yasunori Goto
2007-04-04 12:14 ` tgh
2007-04-04 12:33 ` Yasunori Goto
2007-04-05 2:03 ` tgh
2007-04-05 6:07 ` Yasunori Goto
2007-04-05 8:50 ` tgh
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=4611BF4D.6020002@ncic.ac.cn \
--to=tianguanhua@ncic.ac.cn \
--cc=linux-hotplug@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 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.