From: Paul Jackson <pj@sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: rientjes@google.com, akpm@linux-foundation.org, ak@suse.de,
clameter@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] cpusets: add memory_spread_user option
Date: Fri, 26 Oct 2007 10:54:31 -0700 [thread overview]
Message-ID: <20071026105431.77d56253.pj@sgi.com> (raw)
In-Reply-To: <1193420627.5032.46.camel@localhost>
> Will it handle the case of MPOL_INTERLEAVE policy on a shm segment that
> is mapped by tasks in different, possibly disjoint, cpusets. Local
> allocation does, and my patch does. That was one of the primary
> goals--to address an issue that Christoph has with shared policies.
> cpusets really muck these up!
It probably won't handle that. I don't get along too well with shmem.
Can you to an anti-shmem bigot how MPOL_INTERLEAVE should work with
shmem segments mapped in diverse ways by different tasks in different
cpusets? What would be the key attribute(s) of a proper solution?
Maybe if we keep it simple enough, I can avoid mucking it up too much
this time around.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2007-10-26 17:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 2:14 [patch 1/3] cpusets: extract mmarray loading from update_nodemask David Rientjes
2007-10-26 2:14 ` [patch 2/3] mempolicy: mpol_rebind_policy cleanup David Rientjes
2007-10-26 2:14 ` [patch 3/3] cpusets: add memory_spread_user option David Rientjes
2007-10-26 6:04 ` Paul Jackson
2007-10-26 9:23 ` David Rientjes
2007-10-26 9:56 ` Paul Jackson
2007-10-26 17:18 ` Paul Jackson
2007-10-26 17:39 ` Christoph Lameter
2007-10-26 17:43 ` Paul Jackson
2007-10-26 17:43 ` Lee Schermerhorn
2007-10-26 17:54 ` Paul Jackson [this message]
2007-10-26 18:00 ` Christoph Lameter
2007-10-26 20:39 ` Lee Schermerhorn
2007-10-26 20:41 ` David Rientjes
2007-10-26 2:46 ` [patch 2/3] mempolicy: mpol_rebind_policy cleanup Paul Jackson
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=20071026105431.77d56253.pj@sgi.com \
--to=pj@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.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