linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	kenchen@google.com, jschopp@austin.ibm.com, apw@shadowen.org,
	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: [PATCH] Add a movablecore= parameter for sizing ZONE_MOVABLE
Date: Sat, 14 Jul 2007 14:02:08 +0100	[thread overview]
Message-ID: <20070714130207.GA15864@skynet.ie> (raw)
In-Reply-To: <20070714082807.GC1198@wotan.suse.de>

On (14/07/07 10:28), Nick Piggin didst pronounce:
> On Fri, Jul 13, 2007 at 04:56:10PM +0100, Mel Gorman wrote:
> > On (12/07/07 22:32), Mel Gorman didst pronounce:
> > 
> > > > 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?
> > > 
> > > Well, yes please from me obviously :) . There is one additional patch
> > > I would like to send on tomorrow and that is providing the movablecore=
> > 
> > This is the patch. It has been boot-tested on a number of machines and
> > behaves as expected. Nick, with this in addition, do you have any
> > objection to the ZONE_MOVABLE patches going through to 2.6.23?
> 
> What's the status of making it configurable? I didn't see something
> in -mm for that yet?
> 

I have a patch that makes it configurable but Kamezawa-san posted a very
promising patch about making all zones configurable in a very clever way
which is more general than what I did. He posted it as an RFC[1] and there
was feedback from Andy Whitcroft on how it could be made better so it wouldn't
have been picked up for -mm but something is in the pipeline.

I've tested his patch for zone movable and it worked as advertised so I
intended to see post-merge window what else could be done with it clean-up
wise. I am curious to see if it can also make ZONE_NORMAL configurable on
machines that only have ZONE_DMA for example.

> But that's not as important as ensuring the concept and user visible
> stuff is in good shape, which I no longer have any problems with.

Excellent.

> So
> yeah I think it would be good to get this in and get people up and
> running with it.

Thanks Nick.

[1] http://marc.info/?l=linux-mm&m=118405871911268&w=2

-- 
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>

  reply	other threads:[~2007-07-14 13:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 10:20 -mm merge plans -- anti-fragmentation 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 [this message]
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=20070714130207.GA15864@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