From: David Rientjes <rientjes@google.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch for-3.14] mm, mempolicy: fix mempolicy printing in numa_maps
Date: Mon, 27 Jan 2014 16:13:11 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401271610230.17114@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140127130914.GI4963@suse.de>
On Mon, 27 Jan 2014, Mel Gorman wrote:
> > Should we also consider printing the MOF and MORON states so we get a
> > better view of what the actual policy is?
> >
>
> MOF and MORON are separate issues because MOF is exposed to the userspace
> API but not the policies that make up MORON. For MORON, I concluded that
> we should not expose that via numa_maps unless it can be controlled from
> userspace.
>
We print the possible flags for set_mempolicy() which is pretty simple
since there's only one possible flag at any given time, but we don't print
any possible flags for mbind(). If we are to start printing lazy
migrate-on-fault then we should probably print the other flags as well, I
just don't know how long we want lines in numa_maps to be.
--
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 prev parent reply other threads:[~2014-01-28 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 3:12 David Rientjes
2014-01-27 10:50 ` Peter Zijlstra
2014-01-27 13:09 ` Mel Gorman
2014-01-28 0:13 ` David Rientjes [this message]
2014-01-27 11:03 ` Mel Gorman
2014-01-27 23:31 ` David Rientjes
2014-01-28 8:57 ` Mel Gorman
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=alpine.DEB.2.02.1401271610230.17114@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
/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