From: Christoph Lameter <clameter@sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andi Kleen <ak@suse.de>, linux-mm <linux-mm@kvack.org>,
Steve Longerbeam <stevel@mvista.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Query re: mempolicy for page cache pages
Date: Thu, 18 May 2006 11:41:01 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605181139030.20956@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1147976994.5195.123.camel@localhost.localdomain>
On Thu, 18 May 2006, Lee Schermerhorn wrote:
> Yes, for not overburdening any single node. Paul Jackson's
> "spread" patches address this. Actually, for [some of] our platforms,
> we can hardware interleave some % of memory at the cache line level.
> This shows up as a memory-only node. Some folks claim it would be
> beneficial to be able to specify a page cache policy to prefer this
> hardware interleaved node for the page cache. I see that Ray
> Bryant once proposed a patch to define a separate global and
> optional per process policy to be used for page cache pages. This
> also "died on the vine"...
I'd be very interested in some scheme to address the overburdening in a
simple way. Replication may be useful in addition to spreading to limit
the traffic on the NUMA interlink.
--
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:[~2006-05-18 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 17:49 Lee Schermerhorn
2006-05-18 18:12 ` Andi Kleen
2006-05-18 18:29 ` Lee Schermerhorn
2006-05-18 18:41 ` Christoph Lameter [this message]
2006-05-18 18:14 ` Andrew Morton
2006-05-18 19:10 ` Lee Schermerhorn
2006-05-18 18:15 ` Christoph Lameter
2006-05-18 19:27 ` Lee Schermerhorn
2006-05-18 19:53 ` Christoph Lameter
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=Pine.LNX.4.64.0605181139030.20956@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=stevel@mvista.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