From: Christoph Lameter <clameter@engr.sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
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: Mon, 27 Feb 2006 12:36:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602271235200.8242@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060227121605.fb41d505.pj@sgi.com>
On Mon, 27 Feb 2006, Paul Jackson wrote:
> Andi wrote:
> > Is there a way to use it without cpumemsets?
>
> Not that I know of. So far as I can recall, the task->mems_allowed
> field (over which the spreading is done) is only manipulated by the
> cpuset code. So at least what I have here requires cpusets to have
> any useful affect, yes.
Well we could fall back to interleave on the node online map if some sort
of flag is set.
On the other hand setting memory policy to MPOL_INTERLEAVE already
provides that functionality.
next prev parent reply other threads:[~2006-02-27 20:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 7:02 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 [this message]
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
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=Pine.LNX.4.64.0602271235200.8242@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=Simon.Derr@bull.net \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®