From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: question about memory-hotplug
Date: Wed, 04 Apr 2007 10:29:37 +0000 [thread overview]
Message-ID: <20070404181250.0205.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <4611BF4D.6020002@ncic.ac.cn>
> In the traditional linux without sparsemem, there are node-zone-memmap
> mechanism for managing the physical memory,is it right?
Yes.
> while in the sparsemem mechanism, what is the architure of
> node-zone-memmap or node-zone-mem_section[]-mem_map like?
mem_section[] is "static array" which is defined in sparse.c.
So, no pointer is necessary to point mem_section array.
Its index can be found by only pfn like ((pfn >> PFN_SECTION_SHIFT)).
Each mem_section has pointer of mem_map.
In addition, each page->flags has area for saving mem_section's index.
page_to_section() is (page->flags >> SECTIONS_PGSHIFT) & SECTIONS_MASK).
Tracing __pfn_to_page() and __page_to_pfn in
include/asm-generic/memory_model.h will be good answer
for your understanding.
> 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?
2.6.10 or older kernel has bitmaps to manage buddy page. Current
one doesn't have it. Its information is saved in page->private.
Others are same.
1 section size is bigger than MAX_ORDER. So, current buddy system
doensn't concern about section size.
This means memory hotplug unit size is section size. (At least now)
> 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 ?
x86-64 supports both of sparse and non sparse. It is seleced by
kernel config option.
Bye.
--
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 10:29 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
2007-04-04 10:29 ` Yasunori Goto [this message]
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=20070404181250.0205.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).