linux-kernel - Re: [patch -mm 2/2] mempolicy: use default_policy mode instead of MPOL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200803090019.19518.ak@suse.de>
Date:	Sun, 9 Mar 2008 00:19:19 +0100
From:	Andi Kleen <ak@...e.de>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	Paul Jackson <pj@....com>, akpm@...ux-foundation.org,
	clameter@....com, linux-kernel@...r.kernel.org
Subject: Re: [patch -mm 2/2] mempolicy: use default_policy mode instead of MPOL_DEFAULT


> 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



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/