From: Dave Hansen <dave@linux.vnet.ibm.com>
To: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.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, 12 Apr 2011 17:49:06 -0700 [thread overview]
Message-ID: <1302655746.8321.4001.camel@nimitz> (raw)
In-Reply-To: <alpine.DEB.2.00.1104121719430.10966@chino.kir.corp.google.com>
On Tue, 2011-04-12 at 17:22 -0700, David Rientjes wrote:
> On Mon, 11 Apr 2011, Dave Hansen wrote:
> 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.
>
> That doesn't seem like an argument against this patch, it's an improper
> configuration unless the remote memory access has a latency of 2.1x that
> of a local access between those two nodes. If that's the case, then it's
> accurately following the ACPI spec and the VM has made its policy decision
> to enable zone_reclaim_mode as a result.
Heh, if the kernel broke on every system that didn't follow _some_ spec,
it wouldn't boot in very many places.
When you have a hammer, everything looks like a nail. When you're a
BIOS developer, you start thwacking at the kernel with munged ACPI
tables instead of boot options. Folks do this in the real world, and I
think if we can't put their names and addresses next to the code that
works around this, we might as well put the DMI strings of their
hardware. :)
-- Dave
--
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>
next prev parent reply other threads:[~2011-04-13 0:49 UTC|newest]
Thread overview: 15+ 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 21:19 ` Andrew Morton
2011-04-12 0:59 ` KOSAKI Motohiro
2011-04-11 21:29 ` Dave Hansen
2011-04-12 1:01 ` KOSAKI Motohiro
2011-04-12 2:27 ` Dave Hansen
2011-04-12 7:25 ` KOSAKI Motohiro
2011-05-24 20:07 ` Andrew Morton
2011-05-24 20:24 ` David Rientjes
2011-05-24 20:37 ` Dave Hansen
2011-04-13 0:22 ` David Rientjes
2011-04-13 0:49 ` Dave Hansen [this message]
2011-04-13 0:56 ` David Rientjes
2011-04-13 0:16 ` David Rientjes
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=1302655746.8321.4001.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.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 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).