All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mel@skynet.ie (Mel Gorman)
Cc: npiggin@suse.de, 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: -mm merge plans -- anti-fragmentation
Date: Thu, 12 Jul 2007 12:29:25 -0700	[thread overview]
Message-ID: <20070712122925.192a6601.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070710102043.GA20303@skynet.ie>

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?

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@skynet.ie>
Cc: npiggin@suse.de, 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: -mm merge plans -- anti-fragmentation
Date: Thu, 12 Jul 2007 12:29:25 -0700	[thread overview]
Message-ID: <20070712122925.192a6601.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070710102043.GA20303@skynet.ie>

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?

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

  parent reply	other threads:[~2007-07-12 19:31 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 10:20 -mm merge plans -- anti-fragmentation Mel Gorman
2007-07-10 10:20 ` Mel Gorman
2007-07-10 11:01 ` KAMEZAWA Hiroyuki
2007-07-10 11:01   ` KAMEZAWA Hiroyuki
2007-07-10 11:12   ` Mel Gorman
2007-07-10 11:12     ` Mel Gorman
2007-07-10 11:38     ` KAMEZAWA Hiroyuki
2007-07-10 11:38       ` KAMEZAWA Hiroyuki
2007-07-10 15:50       ` Mel Gorman
2007-07-10 15:50         ` Mel Gorman
2007-07-10 11:04 ` Peter Zijlstra
2007-07-10 11:04   ` Peter Zijlstra
2007-07-10 13:24   ` Mel Gorman
2007-07-10 13:24     ` Mel Gorman
2007-07-10 13:03 ` Nick Piggin
2007-07-10 13:03   ` Nick Piggin
2007-07-10 13:55   ` Mel Gorman
2007-07-10 13:55     ` Mel Gorman
2007-07-10 18:47     ` Christoph Lameter
2007-07-10 18:47       ` Christoph Lameter
2007-07-10 18:46   ` Christoph Lameter
2007-07-10 18:46     ` Christoph Lameter
2007-07-11  9:48     ` Mel Gorman
2007-07-11  9:48       ` Mel Gorman
2007-07-10 14:29 ` Dave McCracken
2007-07-10 14:29   ` Dave McCracken
2007-07-10 15:23   ` Nick Piggin
2007-07-10 15:23     ` Nick Piggin
2007-07-10 17:11     ` Dave McCracken
2007-07-10 17:11       ` Dave McCracken
2007-07-11  2:59       ` Nick Piggin
2007-07-11  2:59         ` Nick Piggin
2007-07-11 10:01         ` Mel Gorman
2007-07-11 10:01           ` Mel Gorman
2007-07-11 13:03         ` Andy Whitcroft
2007-07-11 13:03           ` Andy Whitcroft
2007-07-11  8:55       ` Christoph Hellwig
2007-07-11  8:55         ` Christoph Hellwig
2007-07-10 18:50     ` Christoph Lameter
2007-07-10 18:50       ` Christoph Lameter
2007-07-11 10:05       ` Mel Gorman
2007-07-11 10:05         ` Mel Gorman
2007-07-12 19:29 ` Andrew Morton [this message]
2007-07-12 19:29   ` Andrew Morton
2007-07-12 21:32   ` Mel Gorman
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-13 15:56       ` Mel Gorman
2007-07-14  8:28       ` Nick Piggin
2007-07-14  8:28         ` Nick Piggin
2007-07-14 13:02         ` Mel Gorman
2007-07-14 13:02           ` Mel Gorman
2007-07-15 13:47           ` KAMEZAWA Hiroyuki
2007-07-15 13:47             ` KAMEZAWA Hiroyuki
2007-07-13 10:20   ` -mm merge plans -- anti-fragmentation Andy Whitcroft
2007-07-13 10:20     ` Andy Whitcroft
2007-07-13 16:58     ` Christoph Lameter
2007-07-13 16:58       ` Christoph Lameter
2007-07-13 17:02     ` Nish Aravamudan
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=20070712122925.192a6601.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.