From: mel@skynet.ie (Mel Gorman)
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
npiggin@suse.de, kenchen@google.com, jschopp@austin.ibm.com,
apw@shadowen.org, a.p.zijlstra@chello.nl, y-goto@jp.fujitsu.com,
clameter@sgi.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans -- anti-fragmentation
Date: Tue, 10 Jul 2007 12:12:02 +0100 [thread overview]
Message-ID: <20070710111202.GC25512@skynet.ie> (raw)
In-Reply-To: <20070710200115.b5bbfb4a.kamezawa.hiroyu@jp.fujitsu.com>
On (10/07/07 20:01), KAMEZAWA Hiroyuki didst pronounce:
> On Tue, 10 Jul 2007 11:20:43 +0100
> mel@skynet.ie (Mel Gorman) wrote:
> > > memory-unplug-v7-migration-by-kernel.patch
> > > memory-unplug-v7-isolate_lru_page-fix.patch
> > > memory-unplug-v7-memory-hotplug-cleanup.patch
> > > memory-unplug-v7-page-isolation.patch
> > > memory-unplug-v7-page-offline.patch
> > > memory-unplug-v7-ia64-interface.patch
> > >
> > > These are new, and are dependent on Mel's stuff. Not for 2.6.23.
> > >
> >
> > Specifically, they depend on grouping pages by mobility for the page
> > isolation patch. Without grouping pages by mobility, that patch gets
> > pretty messy. For the operation to succeed at all, it benefits from the
> > ZONE_MOVABLE patches. Kamezawa is cc'd so he might comment further.
> >
>
> In gerneal, there are 2 purpose for memory unplug.
> (1) reduce amount of memory.
> (2) plug some range of memory.
>
> (1) is request from people who use some flexible environment, like virtual machine,
> LPAR. (2) is request from people who want to remove physical DIMM deivces.
>
> For (1), page movable type and page defragment works very well. Because memory unplug
> interface allows removing a section of pages, we need to unplug the whole section.
> By page grouping, pages are grouped into chunks and MOVABLE type chunk can be unplugged
> very easily.
>
> For (2), we need some method for specifing the range we will remove. For doing that,
> ZONE seems to be good candidate. Now we use "kernelcore=" boot option to create
> ZONE_MOVABLE by hand.
At the risk of putting you on the spot, do you mind saying whether the
grouping pages by mobility and ZONE_MOVABLE patches are going in the
direction you want or should something totally different be done? If
they are going the right direction, is there anything critical that is
missing right now?
> But this is the first step. I know Intel guy posted
> his idea to specify Hotpluggable-Memory range in SRAT (by firmware).
There may be additional work required to make this play nicely with
ZONE_MOVABLE but it shouldn't be anything fundamental.
> And I think that
> other method may be introduced for node-hotplug.
>
Same as above really. If the node contains one zone - ZONE_MOVABLE, it
would work for unplugging.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-10 11:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 10:20 Mel Gorman
2007-07-10 11:01 ` KAMEZAWA Hiroyuki
2007-07-10 11:12 ` Mel Gorman [this message]
2007-07-10 11:38 ` KAMEZAWA Hiroyuki
2007-07-10 15:50 ` Mel Gorman
2007-07-10 11:04 ` Peter Zijlstra
2007-07-10 13:24 ` Mel Gorman
2007-07-10 13:03 ` Nick Piggin
2007-07-10 13:55 ` Mel Gorman
2007-07-10 18:47 ` Christoph Lameter
2007-07-10 18:46 ` Christoph Lameter
2007-07-11 9:48 ` Mel Gorman
2007-07-10 14:29 ` Dave McCracken
2007-07-10 15:23 ` Nick Piggin
2007-07-10 17:11 ` Dave McCracken
2007-07-11 2:59 ` Nick Piggin
2007-07-11 10:01 ` Mel Gorman
2007-07-11 13:03 ` Andy Whitcroft
2007-07-11 8:55 ` Christoph Hellwig
2007-07-10 18:50 ` Christoph Lameter
2007-07-11 10:05 ` Mel Gorman
2007-07-12 19:29 ` Andrew Morton
2007-07-12 21:32 ` Mel Gorman
2007-07-13 15:56 ` [PATCH] Add a movablecore= parameter for sizing ZONE_MOVABLE Mel Gorman
2007-07-14 8:28 ` Nick Piggin
2007-07-14 13:02 ` Mel Gorman
2007-07-15 13:47 ` KAMEZAWA Hiroyuki
2007-07-13 10:20 ` -mm merge plans -- anti-fragmentation Andy Whitcroft
2007-07-13 16:58 ` Christoph Lameter
2007-07-13 17:02 ` Nish Aravamudan
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=20070710111202.GC25512@skynet.ie \
--to=mel@skynet.ie \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=jschopp@austin.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=y-goto@jp.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