Re: [PATCH/RFC 0/11] Shared Policy Overview

[Christoph Lameter <clameter@sgi.com>]

On Thu, 28 Jun 2007, Lee Schermerhorn wrote:

> Avoid the taking the reference count on the system default policy or the
> current task's task policy.  Note that if show_numa_map() is called from
> the context of a relative of the target task with the same task mempolicy,
> we won't take an extra reference either.  This is safe, because the policy
> remains referenced by the calling task during the mpol_to_str() processing.

I still do not see the rationale for this patchset. This adds more special 
casing. So if we have a vma policy then we suck again?

This all still falls under the category of messing up a bad situation even 
more. Its first necessary to come up with way to consistently handle 
memory policies and improve the interaction with other methods to 
constrain allocations (cpusets, node restrictions for hugetlb etc etc). It 
should improve the situation and not increase special casing or make the 
system more unpreditable.

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