Re: [PATCH 2/2] Fold numa_maps into mempolicy.c

[Paul Jackson <pj@sgi.com>]

> We could make the function local to mempolicy.c if we fold the numa_maps 
> interface into mempolicy.c. That would prevent outside uses of this and so 
> prevent additional outside uses.

Whether or not get_vma_policy is called with a task != current is not
the same question as whether or not some call is made to get_vma_policy
from code not in mm/mempolicy.c

> But then Paul was looking for such a use?

I was just trying to understand the scope of mmap_sem locking in that
code, for some work I am doing in numa_policy_rebind() to rebind vma
mempolicies safely in the current context.  I didn't have a bias as to
what answers I got to my 20^W4 questions, other than that they made
sense to me.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

--
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>