From: tgh <tianguanhua@ncic.ac.cn>
To: linux-hotplug@vger.kernel.org
Subject: Re: question about memory-hotplug
Date: Wed, 04 Apr 2007 08:53:40 +0000 [thread overview]
Message-ID: <46136794.7050108@ncic.ac.cn> (raw)
In-Reply-To: <4611BF4D.6020002@ncic.ac.cn>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2641 bytes --]
Thank you for your reply
Yasunori Goto åé:
> Hello.
>
>
>> 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 ?
>>
>
> Basically, memory hotplug code depends on sparsemem. So, I'll
> recommend that you should see mm/sparse.c too.
> In sparsemem code, mem_map is allocated dynamically, and
> its pointed by mem_section[] array.
>
In the traditional linux without sparsemem, there are node-zone-memmap
mechanism for managing the physical memory,is it right?
while in the sparsemem mechanism, what is the architure of
node-zone-memmap or node-zone-mem_section[]-mem_map like?
and if the sparsemem is on , buddy still does its work in a mem_map as
before or does it work in a new way?
and how does virt-to-phy macro (or something like it) work,when there
are a list of mem_map in the sparsemem system?
> (However, x86-64 code has original code. IIRC, its memmap was allcated
> statically....)
>
does x86-64 not surpport the memory-hotplug,or how does it achieve the
memory-hotplug ?
>
>> 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?
>>
>
> Pgdat and zone can be allocated dynamically for NUMA system,
> but memmap is not pointed by them if sparsemem is on.
>
which structure points it ,mem_section[] does it? then what is the
architure of the node-zone-mem_section[]-mem_map like?
> Thanks for your concern. :-)
>
> ---
> Yasunori Goto
>
>
>
>
>
-------------------------------------------------------------------------
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 prev parent reply other threads:[~2007-04-04 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 2:43 question about memory-hotplug tgh
2007-04-04 5:58 ` Yasunori Goto
2007-04-04 8:53 ` tgh [this message]
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=46136794.7050108@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.