[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1306269424.22505.20.camel@nimitz>
Date: Tue, 24 May 2011 13:37:04 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, Christoph Lameter <cl@...ux.com>,
David Rientjes <rientjes@...gle.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Chris McDermott <lcm@...ux.vnet.ibm.com>
Subject: Re: [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30
On Tue, 2011-05-24 at 13:07 -0700, Andrew Morton wrote:
> On Mon, 11 Apr 2011 19:27:21 -0700
> Dave Hansen <dave@...ux.vnet.ibm.com> wrote:
> > I'll go try and dig for some more specifics on the hardware so we at
> > least have something to test on.
>
> How's that digging coming along?
>
> I'm pretty wobbly about this patch. Perhaps we should set
> RECLAIM_DISTANCE to pi/2 or something, to force people to correctly set
> the dang thing in initscripts.
The original change in the hardware tables was for the benefit of a
benchmark. Said benchmark isn't going to get run on mainline until the
next batch of enterprise distros drops, at which point the hardware
where this was done will be irrelevant for the benchmark. I'm sure any
new hardware will just set this distance to another yet arbitrary value
to make the kernel do what it wants. :)
Also, when the hardware got _set_ to this initially, I complained. So,
I guess I'm getting my way now, with this patch. I'm cool with it:
Acked-by: Dave Hansen <dave@...ux.vnet.ibm.com>
-- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists