From: Ethan Solomita <solo@google.com>
To: Paul Jackson <pj@sgi.com>, Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org
Subject: cpusets vs. mempolicy and how to get interleaving
Date: Fri, 17 Aug 2007 17:22:54 -0700 [thread overview]
Message-ID: <46C63BDE.20602@google.com> (raw)
application to request NUMA interleaving in the face of cpusets and
modifications to mems_allowed. I'm hoping for some advice.
What we want:
Ideally, we want a task to express its preference for interleaved
memory allocations without having to provide a list of nodes. The kernel
will automatically round-robin amongst the task's mems_allowed.
The problem:
At least in our environment, an independent "cpuset manager" process
may choose to rewrite a cpuset's mems file at any time, possibly
increasing or decreasing the number of available nodes. If
weight(mems_allowed) is decreased, the task's MPOL_INTERLEAVE policy's
nodemask will be shrunk to fit the new mems_allowed. If
weight(mems_allowed) is grown, the policy's nodemask will not gain new
nodes.
What we want is for the task to "set it and forget it," i.e. to express
a preference for interleaving and then never worry about NUMA again. If
the nodemask sent via sys_mempolicy(MPOL_INTERLEAVE) served as a mask
against mems_allowed, then we would specify an all-1s nodemask.
I realize that this doesn't work with backwards compatibility so I'm
looking for advice. A new policy MPOL_INTERLEAVE_ALL that doesn't take a
nodemask argument and interleaves within mems_allowed? Any better
suggestions?
Thanks!
-- Ethan
--
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 reply other threads:[~2007-08-18 0:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 0:22 Ethan Solomita [this message]
2007-08-18 0:29 ` cpusets vs. mempolicy and how to get interleaving Ethan Solomita
2007-08-19 10:18 ` David Rientjes
2007-08-20 0:53 ` Ethan Solomita
2007-08-20 2:34 ` Paul Jackson
2007-08-20 5:47 ` Ethan Solomita
2007-08-20 5:53 ` Paul Jackson
2007-08-20 8:10 ` David Rientjes
2007-08-20 18:25 ` Paul Jackson
2007-08-20 18:28 ` Ethan Solomita
2007-08-20 18:40 ` David Rientjes
2007-08-20 19:50 ` Ethan Solomita
2007-08-20 19:07 ` Christoph Lameter
2007-08-21 14:14 ` Lee Schermerhorn
2007-08-18 1:07 ` Christoph Lameter
2007-08-18 1:51 ` Ethan Solomita
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=46C63BDE.20602@google.com \
--to=solo@google.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=pj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.