From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
Linux-Node-Hotplug <lhns-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>,
"BRADLEY CHRISTIANSEN [imap]" <bradc1@us.ibm.com>
Subject: Re: [Lhns-devel] Merging Nonlinear and Numa style memory hotplug
Date: Wed, 23 Jun 2004 15:32:53 -0700 [thread overview]
Message-ID: <1088029973.28102.269.camel@nighthawk> (raw)
In-Reply-To: <20040622114733.30A6.YGOTO@us.fujitsu.com>
First of all, thank you for merging nonlinear on top of your current
work. It looks very promising.
On Tue, 2004-06-22 at 12:00, Yasunori Goto wrote:
> - Some of strucure's member are added to mem_section[] to
> unify between nonlinear and node style hotplug.
This quadruples the size of the mem_section[] array, and makes each
mem_section entry take up a whole cache line. Are you sure all of these
structure members are needed? Can they be allocated elsewhere, instead
of directly inside the translation tables, or otherwise derived? Also,
why does the booked/free_count have to be kept here? Can't that be
determined by simply looping through and looking at all the pages'
flags?
Also, can you provide a patch which is just your modifications to Dave's
original nonlinear patch?
Instead of remove_from_freelist(unsigned int section), I'd hope that we
could support a much more generic interface in the page allocator:
allocate by physical address. remove_from_freelist() has some intimate
knowledge of the buddy allocator that I think is a bit complex.
That also brings up a more important issue. I see nonlinear as a
back-end for only the page_to_pfn() and pfn_to_page(), and that's all.
There are no real exposures of the nonlinear section size or the
structures to any other part of the kernel because they're all wrapped
up in those functions. It may be possible to keep the entire kernel
oblivious of nonlinear, but I think it's a worthy goal. That's why I'd
like to see the buddy allocator modifications be limited to
currently-existing concepts like physical addresses.
Brad, do you have anything that you can post to demonstrate your
approach for doing allocation by address?
-- Dave
--
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>
next prev parent reply other threads:[~2004-06-23 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:00 Yasunori Goto
2004-06-23 22:32 ` Dave Hansen [this message]
2004-06-24 3:04 ` [Lhns-devel] " Yasunori Goto
2004-06-24 3:26 ` Dave Hansen
2004-06-24 13:28 ` [Lhms-devel] " Dave Hansen
2004-06-24 22:19 ` Yasunori Goto
2004-06-24 22:37 ` Dave Hansen
2004-06-25 3:11 ` [Lhms-devel] " Yasunori Goto
2004-06-25 3:19 ` Dave Hansen
2004-06-25 18:48 ` Yasunori Goto
2004-06-25 18:59 ` Dave Hansen
2004-06-25 20:45 ` Yasunori Goto
2004-06-25 20:49 ` Dave Hansen
2004-06-25 20:54 ` Dave Hansen
2004-06-25 4:49 ` [Lhms-devel] Re: [Lhns-devel] " Shai Fultheim
2004-06-25 15:16 ` Dave Hansen
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=1088029973.28102.269.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=bradc1@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=lhns-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox