All of lore.kernel.org
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lee.Schermerhorn@hp.com, pj@sgi.com, ak@suse.de,
	kamezawa.hiroyu@jp.fujitsu.com, clameter@sgi.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2
Date: Thu, 9 Aug 2007 21:51:27 +0100	[thread overview]
Message-ID: <20070809205126.GA8746@skynet.ie> (raw)
In-Reply-To: <20070809131943.64cb0921.akpm@linux-foundation.org>

On (09/08/07 13:19), Andrew Morton didst pronounce:
> On Wed,  8 Aug 2007 17:15:04 +0100 (IST)
> Mel Gorman <mel@csn.ul.ie> wrote:
> 
> > The following patches replace multiple zonelists per node with one zonelist
> > that is filtered based on the GFP flags.
> 
> I think I'll duck this for now on im-trying-to-vaguely-stabilize-mm grounds.
> Let's go with the horrible-hack for 2.6.23, then revert it and get this
> new approach merged and stabilised over the next week or two?
> 

I'm happy with that plan. I am about to release V3 of the one-zonelist
patchset that includes optimisations so I'm reasonably confident we can
get it to a state we like over the next few weeks.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

WARNING: multiple messages have this Message-ID (diff)
From: mel@skynet.ie (Mel Gorman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lee.Schermerhorn@hp.com, pj@sgi.com, ak@suse.de,
	kamezawa.hiroyu@jp.fujitsu.com, clameter@sgi.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2
Date: Thu, 9 Aug 2007 21:51:27 +0100	[thread overview]
Message-ID: <20070809205126.GA8746@skynet.ie> (raw)
In-Reply-To: <20070809131943.64cb0921.akpm@linux-foundation.org>

On (09/08/07 13:19), Andrew Morton didst pronounce:
> On Wed,  8 Aug 2007 17:15:04 +0100 (IST)
> Mel Gorman <mel@csn.ul.ie> wrote:
> 
> > The following patches replace multiple zonelists per node with one zonelist
> > that is filtered based on the GFP flags.
> 
> I think I'll duck this for now on im-trying-to-vaguely-stabilize-mm grounds.
> Let's go with the horrible-hack for 2.6.23, then revert it and get this
> new approach merged and stabilised over the next week or two?
> 

I'm happy with that plan. I am about to release V3 of the one-zonelist
patchset that includes optimisations so I'm reasonably confident we can
get it to a state we like over the next few weeks.

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

  parent reply	other threads:[~2007-08-09 20:51 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 16:15 [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2 Mel Gorman
2007-08-08 16:15 ` Mel Gorman
2007-08-08 16:15 ` [PATCH 1/3] Use zonelists instead of zones when direct reclaiming pages Mel Gorman
2007-08-08 16:15   ` Mel Gorman
2007-08-08 17:38   ` Christoph Lameter
2007-08-08 17:38     ` Christoph Lameter
2007-08-08 21:06     ` Mel Gorman
2007-08-08 21:06       ` Mel Gorman
2007-08-08 16:15 ` [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists Mel Gorman
2007-08-08 16:15   ` Mel Gorman
2007-08-08 17:46   ` Christoph Lameter
2007-08-08 17:46     ` Christoph Lameter
2007-08-08 21:10     ` Mel Gorman
2007-08-08 21:10       ` Mel Gorman
2007-08-08 23:28       ` Christoph Lameter
2007-08-08 23:28         ` Christoph Lameter
2007-08-08 16:16 ` [PATCH 3/3] Apply MPOL_BIND policy to two highest zones when highest is ZONE_MOVABLE Mel Gorman
2007-08-08 16:16   ` Mel Gorman
2007-08-08 17:36 ` [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2 Christoph Lameter
2007-08-08 17:36   ` Christoph Lameter
2007-08-08 18:30   ` Lee Schermerhorn
2007-08-08 18:30     ` Lee Schermerhorn
2007-08-08 21:44     ` Mel Gorman
2007-08-08 21:44       ` Mel Gorman
2007-08-08 22:40       ` Lee Schermerhorn
2007-08-08 22:40         ` Lee Schermerhorn
2007-08-08 23:37         ` Christoph Lameter
2007-08-08 23:37           ` Christoph Lameter
2007-08-09 14:47         ` Mel Gorman
2007-08-09 14:47           ` Mel Gorman
2007-08-08 23:35       ` Christoph Lameter
2007-08-08 23:35         ` Christoph Lameter
2007-08-08 21:04   ` Mel Gorman
2007-08-08 21:04     ` Mel Gorman
2007-08-08 23:26     ` Christoph Lameter
2007-08-08 23:26       ` Christoph Lameter
2007-08-09 20:19 ` Andrew Morton
2007-08-09 20:19   ` Andrew Morton
2007-08-09 20:33   ` Christoph Lameter
2007-08-09 20:33     ` Christoph Lameter
2007-08-09 20:51   ` Mel Gorman [this message]
2007-08-09 20:51     ` Mel Gorman
2007-08-09 21:20   ` Andi Kleen
2007-08-09 21:20     ` Andi Kleen
2007-08-09 21:40     ` Christoph Lameter
2007-08-09 21:40       ` Christoph Lameter

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=20070809205126.GA8746@skynet.ie \
    --to=mel@skynet.ie \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.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.