From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@linux-foundation.org, ak@suse.de, clameter@sgi.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
balbir@linux.vnet.ibm.com, Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH 0/6] Use one zonelist per node instead of multiple zonelists v5 (resend)
Date: Wed, 12 Sep 2007 16:27:33 -0400 [thread overview]
Message-ID: <1189628853.5004.66.camel@localhost> (raw)
In-Reply-To: <20070911213006.23507.19569.sendpatchset@skynet.skynet.ie>
On Tue, 2007-09-11 at 22:30 +0100, Mel Gorman wrote:
> (Sorry for the resend, I mucked up the TO: line in the earlier sending)
>
> This is the latest version of one-zonelist and it should be solid enough
> for wider testing. To briefly summarise, the patchset replaces multiple
> zonelists-per-node with one zonelist that is filtered based on nodemask and
> GFP flags. I've dropped the patch that replaces inline functions with macros
> from the end as it obscures the code for something that may or may not be a
> performance benefit on older compilers. If we see performance regressions that
> might have something to do with it, the patch is trivially to bring forward.
>
> Andrew, please merge to -mm for wider testing and consideration for merging
> to mainline. Minimally, it gets rid of the hack in relation to ZONE_MOVABLE
> and MPOL_BIND.
Mel:
I'm just getting to this after sorting out an issue with the memory
controller stuff in 23-rc4-mm1. I'm building all my kernels with the
memory controller enabled now, as it hits areas that I'm playing in. I
wanted to give you a heads up that vmscan.c doesn't build with
CONTAINER_MEM_CONT configured with your patches. I won't get to this
until tomorrow. Since you're a few hours ahead of me, you might want to
take a look. No worries, if you don't get a chance...
Later,
Lee
--
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-09-12 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 21:30 Mel Gorman
2007-09-11 21:30 ` [PATCH 1/6] Use zonelists instead of zones when direct reclaiming pages Mel Gorman
2007-09-11 21:30 ` [PATCH 2/6] Introduce node_zonelist() for accessing the zonelist for a GFP mask Mel Gorman
2007-09-11 21:31 ` [PATCH 3/6] Use two zonelist that are filtered by " Mel Gorman
2007-09-11 21:31 ` [PATCH 4/6] Embed zone_id information within the zonelist->zones pointer Mel Gorman
2007-09-12 7:51 ` KAMEZAWA Hiroyuki
2007-09-12 8:32 ` Mel Gorman
2007-09-12 17:06 ` Christoph Lameter
2007-09-11 21:31 ` [PATCH 5/6] Filter based on a nodemask as well as a gfp_mask Mel Gorman
2007-09-11 21:32 ` [PATCH 6/6] Use one zonelist that is filtered by nodemask Mel Gorman
2007-09-12 20:27 ` Lee Schermerhorn [this message]
2007-09-13 10:11 ` [PATCH 0/6] Use one zonelist per node instead of multiple zonelists v5 (resend) Mel Gorman
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=1189628853.5004.66.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=eric.whitney@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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