From: Mel Gorman <mel@csn.ul.ie>
To: Robin Holt <holt@sgi.com>
Cc: Rik van Riel <riel@redhat.com>,
Christoph Lameter <cl@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-ia64@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [PATCH v4] zone_reclaim is always 0 by default
Date: Tue, 9 Jun 2009 11:37:55 +0100 [thread overview]
Message-ID: <20090609103754.GN18380@csn.ul.ie> (raw)
In-Reply-To: <20090609095507.GA9851@attica.americas.sgi.com>
On Tue, Jun 09, 2009 at 04:55:07AM -0500, Robin Holt wrote:
> On Mon, Jun 08, 2009 at 12:50:48PM +0100, Mel Gorman wrote:
>
> Let me start by saying I agree completely with everything you wrote and
> still disagree with this patch, but was willing to compromise and work
> around this for our upcoming x86_64 machine by putting a "value add"
> into our packaging of adding a sysctl that turns reclaim back on.
>
To be honest, I'm more leaning towards a NACK than an ACK on this one. I
don't support enough NUMA machines to feel strongly enough about it but
unconditionally setting zone_reclaim_mode to 0 on x86-64 just because i7's
might be there seems ill-advised to me and will have other consequences for
existing more traditional x86-64 NUMA machines.
> ...
> > > Index: b/arch/powerpc/include/asm/topology.h
> > > ===================================================================
> > > --- a/arch/powerpc/include/asm/topology.h
> > > +++ b/arch/powerpc/include/asm/topology.h
> > > @@ -10,6 +10,12 @@ struct device_node;
> > >
> > > #include <asm/mmzone.h>
> > >
> > > +/*
> > > + * Distance above which we begin to use zone reclaim
> > > + */
> > > +#define RECLAIM_DISTANCE 20
> > > +
> > > +
> >
> > Where is the ia-64-specific modifier to RECAIM_DISTANCE?
>
> It was already defined as 15 in arch/ia64/include/asm/topology.h
>
/me slaps self
thanks
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2009-06-09 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 10:23 [PATCH v4] zone_reclaim is always 0 by default KOSAKI Motohiro
2009-06-04 10:59 ` Wu Fengguang
2009-06-04 12:24 ` Robin Holt
2009-06-08 11:50 ` Mel Gorman
2009-06-09 9:55 ` Robin Holt
2009-06-09 10:37 ` Mel Gorman [this message]
2009-06-09 12:02 ` Robin Holt
2009-06-09 19:47 ` Andrew Morton
2009-06-09 13:48 ` KOSAKI Motohiro
2009-06-09 14:38 ` 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=20090609103754.GN18380@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=holt@sgi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=riel@redhat.com \
--cc=yanmin.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).