From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Fw: [Lhms-devel] Making hotremovable attribute with memory section[0/4]
Date: Mon, 16 Aug 2004 16:35:50 -0700 [thread overview]
Message-ID: <1092699350.1822.43.camel@nighthawk> (raw)
In-Reply-To: <20040816153613.E6F7.YGOTO@us.fujitsu.com>
On Mon, 2004-08-16 at 15:56, Yasunori Goto wrote:
> I made new patches for Memory hotplug.
> Dave Hansen-san recommeded me I should forward these to LKML
> or linux-mm.
> So, I'll forword these.
I think I suggested that you forward _one_ ;)
In any case, the question of the day is, does anyone have any
suggestions on how to create 2 separate pools for pages: one
representing hot-removable pages, and the other pages that may not be
removed?
Yasunori's patch takes the approach of creating a new free_area struct
inside each zone. Another approach might be to actually create new
'struct zones' for the new areas. The new zones one seems cleaner to
me, but the implementation might end up rippling in to a lot of
different areas of code.
-- 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-08-16 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 22:56 Yasunori Goto
2004-08-16 23:35 ` Dave Hansen [this message]
2004-08-17 0:27 ` Alan Cox
2004-08-17 5:15 ` Yasunori Goto
2004-08-17 9:58 ` Dave Jones
2004-08-17 7:52 ` Fw: " 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=1092699350.1822.43.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--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