From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mel@skynet.ie>,
npiggin@suse.de, kenchen@google.com, jschopp@austin.ibm.com,
kamezawa.hiroyu@jp.fujitsu.com, 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: Fri, 13 Jul 2007 11:20:25 +0100 [thread overview]
Message-ID: <469751E9.7060904@shadowen.org> (raw)
In-Reply-To: <20070712122925.192a6601.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 10 Jul 2007 11:20:43 +0100
> mel@skynet.ie (Mel Gorman) wrote:
>
>>> create-the-zone_movable-zone.patch
>>> allow-huge-page-allocations-to-use-gfp_high_movable.patch
>>> handle-kernelcore=-generic.patch
>>>
>>> Mel's moveable-zone work. In a similar situation. We need to stop whatever
>>> we're doing and get down and work out what we're going to do with all this
>>> stuff.
>>>
>> Whatever about grouping pages by mobility, I would like to see these go
>> through. They have a real application for hugetlb pool resizing where the
>> administrator knows the range of hugepages that will be required but doesn't
>> want to waste memory when the required number of hugepages is small. I've
>> cc'd Kenneth Chen as I believe he has run into this problem recently where
>> I believe partitioning memory would have helped. He'll either confirm or deny.
>
> Still no decision here, really.
>
> Should we at least go for
>
> add-__gfp_movable-for-callers-to-flag-allocations-from-high-memory-that-may-be-migrated.patch
> create-the-zone_movable-zone.patch
> allow-huge-page-allocations-to-use-gfp_high_movable.patch
> handle-kernelcore=-generic.patch
>
> in 2.6.23?
These patches are pretty simple and self-contained utilising the
existing zone infrastructure. They provide a significant degree of
placement control when configured, which gives a lot of the benefits of
grouping-pages-by-mobility. Merging these would seem like a low-risk
option.
Having a degree of placement control as delivered by ZONE_MOVABLE
greatly increases the effectiveness of lumpy reclaim at higher orders.
These patches plus lumpy would (IMO) provide a good base for further
development. In particular I would envisage better usability for
hugepage users in terms of simpler configuration.
I would like to see ZONE_MOVABLE and lumpy considered for 2.6.23.
-apw
--
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-13 10:20 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
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 ` Andy Whitcroft [this message]
2007-07-13 16:58 ` -mm merge plans -- anti-fragmentation 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=469751E9.7060904@shadowen.org \
--to=apw@shadowen.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.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=mel@skynet.ie \
--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