All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Chris McDermott <lcm@linux.vnet.ibm.com>
Subject: Re: [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30
Date: Tue, 24 May 2011 13:07:00 -0700	[thread overview]
Message-ID: <20110524130700.079b09e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <1302575241.7286.17853.camel@nimitz>

On Mon, 11 Apr 2011 19:27:21 -0700
Dave Hansen <dave@linux.vnet.ibm.com> wrote:

> On Tue, 2011-04-12 at 10:01 +0900, KOSAKI Motohiro wrote:
> > > On Mon, 2011-04-11 at 17:19 +0900, KOSAKI Motohiro wrote:
> > > > This patch raise zone_reclaim_mode threshold to 30. 30 don't have
> > > > specific meaning. but 20 mean one-hop QPI/Hypertransport and such
> > > > relatively cheap 2-4 socket machine are often used for tradiotional
> > > > server as above. The intention is, their machine don't use
> > > > zone_reclaim_mode.
> > > 
> > > I know specifically of pieces of x86 hardware that set the information
> > > in the BIOS to '21' *specifically* so they'll get the zone_reclaim_mode
> > > behavior which that implies.
> > 
> > Which hardware?
> 
> I'd have to go digging for the model numbers.  I just remember having
> discussions with folks about it a couple of years ago.  My memory isn't
> what it used to be. :)
> 
> > The reason why now we decided to change default is the original bug reporter was using
> > mere commodity whitebox hardware and very common workload. 
> > If it is enough commotidy, we have to concern it. but if it is special, we don't care it.
> > Hardware vendor should fix a firmware.
> 
> Yeah, it's certainly a "simple" fix.  The distance tables can certainly
> be adjusted easily, and worked around pretty trivially with boot
> options.  If we decide to change the generic case, let's also make sure
> that we put something else in place simultaneously that is nice for the
> folks that don't want it changed.  Maybe something DMI-based that digs
> for model numbers?
> 
> 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.


WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Chris McDermott <lcm@linux.vnet.ibm.com>
Subject: Re: [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30
Date: Tue, 24 May 2011 13:07:00 -0700	[thread overview]
Message-ID: <20110524130700.079b09e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <1302575241.7286.17853.camel@nimitz>

On Mon, 11 Apr 2011 19:27:21 -0700
Dave Hansen <dave@linux.vnet.ibm.com> wrote:

> On Tue, 2011-04-12 at 10:01 +0900, KOSAKI Motohiro wrote:
> > > On Mon, 2011-04-11 at 17:19 +0900, KOSAKI Motohiro wrote:
> > > > This patch raise zone_reclaim_mode threshold to 30. 30 don't have
> > > > specific meaning. but 20 mean one-hop QPI/Hypertransport and such
> > > > relatively cheap 2-4 socket machine are often used for tradiotional
> > > > server as above. The intention is, their machine don't use
> > > > zone_reclaim_mode.
> > > 
> > > I know specifically of pieces of x86 hardware that set the information
> > > in the BIOS to '21' *specifically* so they'll get the zone_reclaim_mode
> > > behavior which that implies.
> > 
> > Which hardware?
> 
> I'd have to go digging for the model numbers.  I just remember having
> discussions with folks about it a couple of years ago.  My memory isn't
> what it used to be. :)
> 
> > The reason why now we decided to change default is the original bug reporter was using
> > mere commodity whitebox hardware and very common workload. 
> > If it is enough commotidy, we have to concern it. but if it is special, we don't care it.
> > Hardware vendor should fix a firmware.
> 
> Yeah, it's certainly a "simple" fix.  The distance tables can certainly
> be adjusted easily, and worked around pretty trivially with boot
> options.  If we decide to change the generic case, let's also make sure
> that we put something else in place simultaneously that is nice for the
> folks that don't want it changed.  Maybe something DMI-based that digs
> for model numbers?
> 
> 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.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-05-24 20:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  8:19 [PATCH resend^2] mm: increase RECLAIM_DISTANCE to 30 KOSAKI Motohiro
2011-04-11  8:19 ` KOSAKI Motohiro
2011-04-11 21:19 ` Andrew Morton
2011-04-11 21:19   ` Andrew Morton
2011-04-12  0:59   ` KOSAKI Motohiro
2011-04-12  0:59     ` KOSAKI Motohiro
2011-04-11 21:29 ` Dave Hansen
2011-04-11 21:29   ` Dave Hansen
2011-04-12  1:01   ` KOSAKI Motohiro
2011-04-12  1:01     ` KOSAKI Motohiro
2011-04-12  2:27     ` Dave Hansen
2011-04-12  2:27       ` Dave Hansen
2011-04-12  7:25       ` KOSAKI Motohiro
2011-04-12  7:25         ` KOSAKI Motohiro
2011-05-24 20:07       ` Andrew Morton [this message]
2011-05-24 20:07         ` Andrew Morton
2011-05-24 20:24         ` David Rientjes
2011-05-24 20:24           ` David Rientjes
2011-05-24 20:37         ` Dave Hansen
2011-05-24 20:37           ` Dave Hansen
2011-04-13  0:22   ` David Rientjes
2011-04-13  0:22     ` David Rientjes
2011-04-13  0:49     ` Dave Hansen
2011-04-13  0:49       ` Dave Hansen
2011-04-13  0:56       ` David Rientjes
2011-04-13  0:56         ` David Rientjes
2011-04-13  0:16 ` David Rientjes
2011-04-13  0:16   ` David Rientjes
2011-04-13  0:26   ` Rob Mueller
2011-04-13  0:26     ` Rob Mueller

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=20110524130700.079b09e8.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=lcm@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.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.