From: viro@parcelfarce.linux.theplanet.co.uk
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Chris Wright <chrisw@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>, Tim Hockin <thockin@hockin.org>,
Mike Waychison <Michael.Waychison@Sun.COM>,
ReiserFS List <reiserfs-list@namesys.com>,
Hans Reiser <reiser@namesys.com>
Subject: Re: Using fs views to isolate untrusted processes: I need an assistant architect in the USA for Phase I of a DARPA funded linux kernel project
Date: Thu, 26 Aug 2004 06:01:45 +0100 [thread overview]
Message-ID: <20040826050145.GT21964@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <C08CA144-F71B-11D8-A7C9-000393ACC76E@mac.com>
On Thu, Aug 26, 2004 at 12:52:37AM -0400, Kyle Moffett wrote:
> Where would I increase the hash size if I wanted to increase the number
> of bindings by an order of magnitude or so? I'm very interested in
> pursuing this possibility, because when combined with the procedure I
> described earlier, plus a little bit of extra work with capabilities
> and such
> it's very easy to build incredibly flexible and basically indestructible
> chroot environments with not much code.
*shrug*
fs/namespace.c::mnt_init(). Right now it allocates 1 page for hash table
(order = 0), you can easily raise that. You might want to try and change
the order of checks in lookup_mnt() loop - depending on your setup it
might speed the things up, but I doubt that it would be noticable win.
next prev parent reply other threads:[~2004-08-26 5:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 1:20 Hans Reiser
2004-08-25 20:25 ` Rik van Riel
2004-08-25 20:56 ` Tim Hockin
2004-08-25 21:23 ` Mike Waychison
2004-08-26 6:31 ` Hans Reiser
2004-08-26 13:59 ` Stephen Smalley
2004-08-25 23:19 ` Kyle Moffett
2004-08-26 0:16 ` Mike Waychison
2004-08-26 0:50 ` Kyle Moffett
2004-08-26 1:06 ` Chris Wright
2004-08-26 4:16 ` Kyle Moffett
2004-08-26 4:29 ` viro
2004-08-26 4:52 ` Kyle Moffett
2004-08-26 5:01 ` viro [this message]
2004-08-26 0:56 ` Chris Wright
2004-08-26 7:52 ` Hans Reiser
2004-08-26 8:48 ` Hans Reiser
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=20040826050145.GT21964@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=Michael.Waychison@Sun.COM \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=riel@redhat.com \
--cc=thockin@hockin.org \
/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
Powered by JetHome