From: Andi Kleen <ak@suse.de>
To: Paul Jackson <pj@sgi.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
dgc@sgi.com, steiner@sgi.com, Simon.Derr@bull.net,
linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH 01/02] cpuset memory spread slab cache filesys
Date: Tue, 28 Feb 2006 18:13:46 +0100 [thread overview]
Message-ID: <200602281813.47234.ak@suse.de> (raw)
In-Reply-To: <20060227175603.e858eade.pj@sgi.com>
On Tuesday 28 February 2006 02:56, Paul Jackson wrote:
> Hmmm ... your thread with Andi confuses me ...
>
> Oh well.
>
> I take it that Andi is suggesting that there be the option to override
> the tasks mempolicy, in the particular case of these file i/o slab
> caches, with an interleave over the online nodes.
Yep exactly.
> This option would be useful in the case that a system is not using
> cpusets, but still wants to spread out these particular (sometimes
> large) file i/o caches.
Yep.
> Questions for Andi:
>
> 1) Are you content to have such a interleave of these particular file
> i/o slabs triggered by a mm/mempolicy.c option? Or do you think
> we need some sort of task external API to invoke this policy?
Task external. mempolicy.c has no good way to handle multiple policies
like this. I was thinking of a simple sysctl
I guess I can cook up a patch once your code is merged.
> 2) Do you recommend that the page (file buffer) cache also be
> interleavable, across all online nodes, if optionally requested,
> on systems not using cpusets?
Yes, but as a separate option.
-Andi
next prev parent reply other threads:[~2006-02-28 17:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 7:02 [PATCH 01/02] cpuset memory spread slab cache filesys Paul Jackson
2006-02-27 7:02 ` [PATCH 02/02] cpuset memory spread slab cache format Paul Jackson
2006-02-27 19:34 ` [PATCH 01/02] cpuset memory spread slab cache filesys Andi Kleen
2006-02-27 20:16 ` Paul Jackson
2006-02-27 20:36 ` Christoph Lameter
2006-02-27 20:49 ` Andi Kleen
2006-02-27 20:56 ` Christoph Lameter
2006-02-27 21:02 ` Andi Kleen
2006-02-27 22:14 ` Christoph Lameter
2006-02-27 22:39 ` Andi Kleen
2006-02-27 23:13 ` Christoph Lameter
2006-02-28 1:56 ` Paul Jackson
2006-02-28 17:13 ` Andi Kleen [this message]
2006-03-01 18:27 ` Paul Jackson
2006-03-01 18:34 ` Andi Kleen
2006-03-01 18:38 ` Christoph Lameter
2006-03-01 18:58 ` Paul Jackson
2006-03-01 19:21 ` Andi Kleen
2006-03-01 20:53 ` Paul Jackson
2006-03-01 20:59 ` Andi Kleen
2006-03-01 21:19 ` Paul Jackson
2006-03-01 21:21 ` Andi Kleen
2006-03-01 22:20 ` Christoph Lameter
2006-03-01 22:52 ` Paul Jackson
2006-03-02 1:57 ` Andi Kleen
2006-03-02 14:38 ` 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=200602281813.47234.ak@suse.de \
--to=ak@suse.de \
--cc=Simon.Derr@bull.net \
--cc=clameter@engr.sgi.com \
--cc=clameter@sgi.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=steiner@sgi.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