From: Andy Whitcroft <apw@shadowen.org>
To: Stephen Smalley <sds@epoch.ncsc.mil>, Andrew Morton <akpm@osdl.org>
Cc: anton@samba.org, ak@suse.de, raybry@sgi.com,
lse-tech@lists.sourceforge.net, linux-ia64@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
mbligh@aracnet.com
Subject: Re: [Lse-tech] Re: Hugetlbpages in very large memory
Date: Thu, 18 Mar 2004 22:21:45 +0000 [thread overview]
Message-ID: <378619693.1079648505@[192.168.0.89]> (raw)
In-Reply-To: <1079644967.12704.216.camel@moss-spartans.epoch.ncsc.mil>
--On 18 March 2004 16:22 -0500 Stephen Smalley <sds@epoch.ncsc.mil> wrote:
> On Thu, 2004-03-18 at 15:25, Andrew Morton wrote:
>> Seems reasonable, although "vm_enough_acctdom" makes my eyes pop. Why
>> not keep the "vm_enough_memory" identifier?
>>
>> I've asked Stephen for comment - assuming he's OK with it I'd ask you to
>> finish this off please.
I have no emotional attachment to any of the names. If we can come up with
a more sensible name then all for the best. I was trying to find something
which implied the 'measurement' thing which didn't overlap with any of the
other memory grouping concepts. As the domains overlap nodes and zones.
> To keep the name, he needs to update all callers, right? Current patch
> appears to add a static inline for security_vm_enough_memory that
> retains the old interface to avoid having to update most callers.
Yes this is the main reason for the name change. This is at the dirty hack
stage in that sense, minimal changes to prove the concept. I think that we
should be changing all the callers if this is going mainline in the longer
term. Although then the do cross 4 architecture and with it being in the
security interface it also interfaces with selinux as well (sigh).
I'll put together a more complete change over of the interface, keep the
name the same and see how intrusive that seems. Then we'll get some
testing on it.
> I don't have any fundamental problem with the nature of the change. As
> a side note, patch was malformed (at least as I received it), not sure
> if that was just a problem on my end.
Steven, I'll send you a copy of the patch under separate cover.
-apw
next prev parent reply other threads:[~2004-03-18 22:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 3:44 Hugetlbpages in very large memory machines Ray Bryant
2004-03-13 3:45 ` Ray Bryant
2004-03-13 3:48 ` Andi Kleen
2004-03-13 5:49 ` William Lee Irwin III
2004-03-13 16:10 ` [Lse-tech] " Andi Kleen
2004-03-14 0:05 ` William Lee Irwin III
2004-03-14 5:22 ` Peter Chubb
2004-03-15 23:31 ` Seth, Rohit
2004-03-14 2:45 ` Andrew Morton
2004-03-14 4:06 ` [Lse-tech] " Anton Blanchard
2004-03-17 19:05 ` [Lse-tech] Re: Hugetlbpages in very large memory Andy Whitcroft
2004-03-18 20:25 ` Andrew Morton
2004-03-18 21:22 ` Stephen Smalley
2004-03-18 22:21 ` Andy Whitcroft [this message]
2004-03-23 17:30 ` Andy Whitcroft
2004-03-24 17:38 ` Andy Whitcroft
2004-03-14 8:38 ` [Lse-tech] Re: Hugetlbpages in very large memory machines Ray Bryant
2004-03-14 8:48 ` William Lee Irwin III
2004-03-14 8:57 ` [Lse-tech] Re: Hugetlbpages in very large memory Andrew Morton
2004-03-14 9:02 ` Andrew Morton
2004-03-14 9:07 ` [Lse-tech] Re: Hugetlbpages in very large memory machines William Lee Irwin III
2004-03-15 6:45 ` Ray Bryant
2004-03-15 23:54 ` William Lee Irwin III
2004-03-13 3:55 ` William Lee Irwin III
2004-03-13 4:56 ` Hirokazu Takahashi
2004-03-16 0:30 ` Nobuhiko Yoshida
2004-03-16 1:54 ` Andi Kleen
2004-03-16 2:32 ` Hirokazu Takahashi
2004-03-16 3:20 ` Hirokazu Takahashi
2004-03-16 3:15 ` Nobuhiko Yoshida
2004-04-01 9:10 ` Nobuhiko Yoshida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='378619693.1079648505@[192.168.0.89]' \
--to=apw@shadowen.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=raybry@sgi.com \
--cc=sds@epoch.ncsc.mil \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox