linux-kernel - Re: [patch 1/4] mempolicy: convert MPOL constants to enum

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: <Pine.LNX.4.64.0802111244140.26158@schroedinger.engr.sgi.com>
Date:	Mon, 11 Feb 2008 12:45:45 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	David Rientjes <rientjes@...gle.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Jackson <pj@....com>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [patch 1/4] mempolicy: convert MPOL constants to enum

On Mon, 11 Feb 2008, David Rientjes wrote:

> On Mon, 11 Feb 2008, Christoph Lameter wrote:
> 
> > Then you could follow through with the enum mempolicy thing 
> > throughtout. Why not use enum mempolicy in struct mempolicy?
> > 
> 
> Mempolicy flags, as I implemented them in patch 2 in this series, are not 
> integer constants that are enumerated starting at 0.  They are individual 
> bits that are shifted a pre-defined length and intersected with the 
> enumerated mode.  This allows both the mode and the flags to be stored in 
> the same object.

Ok. Now are you are making the same point that I did before. Lets leave 
enum out if we need to do these tricks with the upper bits.
--
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/