From: Andi Kleen <ak@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Paul Jackson <pj@sgi.com>,
akpm@linux-foundation.org, clameter@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch -mm 2/2] mempolicy: use default_policy mode instead of MPOL_DEFAULT
Date: Sun, 9 Mar 2008 00:19:19 +0100 [thread overview]
Message-ID: <200803090019.19518.ak@suse.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0803081414460.12095@chino.kir.corp.google.com>
> Using MPOL_DEFAULT purely for falling back to the task or system-wide
> policy, however, seems confusing. The semantics seem to indicate that
> MPOL_DEFAULT represents the system-wide default policy without any
> preferred node or set of nodes to bind or interleave. So if a VMA has a
> policy of MPOL_DEFAULT then, to me, it seems like that indicates the
> absence of a specific policy, not a mandate to fallback to the task
> policy.
I designed MPOL_DEFAULT on vma originally to be a fallback to the task policy.
Absence of specific policy would be MPOL_PREFERRED with -1 node.
-Andi
next prev parent reply other threads:[~2008-03-08 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 1:24 [patch -mm 1/2] mempolicy: disallow static or relative flags for local preferred mode David Rientjes
2008-03-08 1:24 ` [patch -mm 2/2] mempolicy: use default_policy mode instead of MPOL_DEFAULT David Rientjes
2008-03-08 1:28 ` Paul Jackson
2008-03-08 1:33 ` David Rientjes
2008-03-08 1:35 ` Paul Jackson
2008-03-08 1:59 ` Christoph Lameter
2008-03-08 2:14 ` David Rientjes
2008-03-08 19:13 ` Lee Schermerhorn
2008-03-08 22:20 ` David Rientjes
2008-03-08 23:19 ` Andi Kleen [this message]
2008-03-10 13:48 ` Lee Schermerhorn
2008-03-10 19:09 ` [patch -mm 1/2] mempolicy: disallow static or relative flags for local preferred mode Andrew Morton
2008-03-10 19:20 ` what to patch Randy Dunlap
2008-03-10 19:55 ` Andrew Morton
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=200803090019.19518.ak@suse.de \
--to=ak@suse.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--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 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.