[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87b4c1b961fcd94c6e34ab314e2c1dff@codeaurora.org>
Date: Mon, 18 Jan 2021 11:45:08 +0530
From: pnagar@...eaurora.org
To: David Howells <dhowells@...hat.com>
Cc: Casey Schaufler <casey@...aufler-ca.com>, arnd@...db.de,
jmorris@...ei.org, serge@...lyn.com, paul@...l-moore.com,
stephen.smalley.work@...il.com, eparis@...isplace.org,
linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
linux-arch@...r.kernel.org, psodagud@...eaurora.org,
nmardana@...eaurora.org, dsule@...eaurora.org,
Joe Perches <joe@...ches.com>, Miguel Ojeda <ojeda@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2] selinux: security: Move selinux_state to a
separate page
On 2021-01-13 16:26, David Howells wrote:
> Casey Schaufler <casey@...aufler-ca.com> wrote:
>
>> >> How would this interact with or complement __read_mostly?
>> >>
>> > Currently, the mechanism we are working on developing is
>> > independent of __read_mostly. This is something we can look more into
>> > while working further on the mechanism.
>>
>> Please either integrate the two or explain how they differ.
>> It appears that you haven't considered how you might exploit
>> or expand the existing mechanism.
>
> I think __read_mostly is about grouping stuff together that's rarely
> going to
> be read to make the CPU's data cache more efficient. It doesn't stop
> people
> writing to such a variable.
>
> David
Thank you for sharing!
Powered by blists - more mailing lists