From: Davide Libenzi <davidel@xmailserver.org>
To: Rik van Riel <riel@redhat.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
Andy Isaacson <adi@hexapodia.org>,
Kyle Moffett <mrmacman_g4@mac.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/4] MAP_NOZERO v2 - VM_NOZERO/MAP_NOZERO early summer madness
Date: Mon, 2 Jul 2007 16:46:52 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707021619590.14774@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <4689826C.5050800@redhat.com>
On Mon, 2 Jul 2007, Rik van Riel wrote:
> Davide Libenzi wrote:
> > On Mon, 2 Jul 2007, Ulrich Drepper wrote:
> >
> > > On 7/2/07, Rik van Riel <riel@redhat.com> wrote:
> > > > That should not happen. The default SELinux configuration
> > > > in Fedora (and Debian?) runs a few daemons in their own
> > > > restricted modes and has most of the system running in
> > > > unconfined_t, including the majority of user programs.
> > > This is the state as of F7. This will change hopefully soon.
> > > Programs like firefox run by normal users must be confined, to. Any
> > > tests using security must be fast, it's not something which is done
> > > only for a few apps.
> >
> > The strong requirement would be that the cookie is not a bit longer than
> > sizeof(unsigned long).
>
> You could easily replace the cookie with a pointer to a free
> page pool.
You talked about this pool even before, but honestly I don't see how it
can help.
Pools requires management (mainly flush under pressure), and it wouldn't
really do any benefit. Don't we already have enough pools in the
allocation path?
The pool has to be UID (or cookie/whatever) based [1], so on top of the
pool lookup/management code, you'll have another lock to be taken (the
pool one). So using the UID (cookie) is simpler, faster and requires no
extra code.
A simple numeric cookie virtually creates "pools" w/out requiring extra
code. Yes, having really separate pool helps the recycle efficency, but
I'm not sure that's worth the extra code.
[1] An mm_struct based pool would be clearly useless
- Davide
next prev parent reply other threads:[~2007-07-02 23:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 18:49 Davide Libenzi
2007-06-29 2:57 ` Kyle Moffett
2007-06-29 3:04 ` Rik van Riel
2007-06-29 5:09 ` Ulrich Drepper
2007-06-29 5:20 ` Davide Libenzi
2007-06-29 19:39 ` Andy Isaacson
2007-06-29 20:12 ` Davide Libenzi
2007-06-29 23:48 ` Kyle Moffett
2007-06-30 19:03 ` Davide Libenzi
2007-06-30 23:46 ` Kyle Moffett
2007-06-30 23:57 ` Davide Libenzi
2007-07-01 0:21 ` Kyle Moffett
2007-07-01 4:25 ` Davide Libenzi
2007-07-02 19:00 ` Andy Isaacson
2007-07-02 19:03 ` Rik van Riel
2007-07-02 19:06 ` Ulrich Drepper
2007-07-02 22:46 ` Davide Libenzi
2007-07-02 22:55 ` Rik van Riel
2007-07-02 23:46 ` Davide Libenzi [this message]
2007-07-04 21:53 ` Andy Isaacson
2007-07-04 23:42 ` Davide Libenzi
2007-07-02 18:38 ` Andy Isaacson
2007-07-02 22:38 ` Davide Libenzi
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=Pine.LNX.4.64.0707021619590.14774@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=adi@hexapodia.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=riel@redhat.com \
/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
all inboxes | Powered by JetHome®