lkml.org 
[lkml]   [2014]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch for-3.14] mm, mempolicy: fix mempolicy printing in numa_maps
On Mon, Jan 27, 2014 at 11:50:11AM +0100, Peter Zijlstra wrote:
> On Sat, Jan 25, 2014 at 07:12:35PM -0800, David Rientjes wrote:
> > As a result of commit 5606e3877ad8 ("mm: numa: Migrate on reference
> > policy"), /proc/<pid>/numa_maps prints the mempolicy for any <pid> as
> > "prefer:N" for the local node, N, of the process reading the file.
> >
> > This should only be printed when the mempolicy of <pid> is MPOL_PREFERRED
> > for node N.
> >
> > If the process is actually only using the default mempolicy for local node
> > allocation, make sure "default" is printed as expected.
>
> 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.

--
Mel Gorman
SUSE Labs


\
 
 \ /
  Last update: 2014-01-27 14:41    [W:0.142 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site