From: Chris Wright <chrisw@osdl.org>
To: Serge Hallyn <serue@us.ibm.com>
Cc: Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] [0/6] LSM Stacking
Date: Thu, 4 Nov 2004 14:52:29 -0800 [thread overview]
Message-ID: <20041104145229.D2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1099609471.2096.10.camel@serge.austin.ibm.com>; from serue@us.ibm.com on Thu, Nov 04, 2004 at 05:04:31PM -0600
* Serge Hallyn (serue@us.ibm.com) wrote:
> The following set of patches add support required to stack most
> LSMs. The most important patch is the first, which provides a
> method for more than one LSM to annotate information to kernel
> objects. LSM's known to use the LSM fields include selinux, bsdjail,
> seclvl, and digsig. Without this patch (or something like it),
> none of these modules can be used together.
I think, all in all, this needs more work and more justification (esp.
w.r.t. overhead and impact on the current common use of a single
module).
> 2. A 2.6.10-rc1-bk10 system with the stacking patches, and capabilities
> and SELinux compiled into the kernel under the stacker LSM. Other
> than stacker being compiled in and the size of the LSM void* array
> being set to 4, the exact same .config was used.
How many CPU's?
> 3. The same kernel as in (2), but with bsdjail and seclvl also stacked.
>
> On each of these configurations, I ran unixbench twice, and compiled
> a kernel twice (with the same .config, and all files in the cached
> each time).
>
> The kernel compilation results are as follows:
>
> No stacking (1) Stacking (2) More Stacking (3)
> Run 1 real 9m51.647s real 9m48.045s real 9m53.292s
> user 8m28.637s user 8m29.108s user 8m33.319s
> sys 1m13.900s sys 1m14.993s sys 1m15.377s
>
> Run 2 real 9m48.154s real 9m53.369s real 9m53.292s
> user 8m28.983s user 8m29.101s user 8m34.407s
> sys 1m13.981s sys 1m15.307s sys 1m15.611s
>
> Run 3 real 9m51.105s real 9m51.840s real 9m58.840s
> user 8m28.894s user 8m29.192s user 8m33.538s
> sys 1m14.183s sys 1m15.345s sys 1m16.146s
>
> Unixbench summaries are as follows. (I can send the full output if
> anyone asks)
Sorry, I forget what the Unixbench scores mean....
> No stacking (1) Stacking (2) More Stacking (3)
> Run 1 651.5 647.1 634.3
> Run 2 648.2 642.8 632.7
How did lmbench numbers look? And other workloads, like network?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-11-04 22:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 23:04 Serge Hallyn
2004-11-04 22:52 ` Chris Wright [this message]
2004-11-05 1:01 ` Serge E. Hallyn
2004-11-05 1:05 ` Chris Wright
2004-11-05 2:16 ` James Morris
2004-11-04 23:06 ` [RFC] [PATCH] [1/6] LSM Stacking: Replace LSM void* with arrays Serge Hallyn
2004-11-04 22:34 ` Chris Wright
2004-11-04 23:08 ` [RFC] [PATCH] [2/6] LSM Stacking: Add stacker LSM Serge Hallyn
2004-11-04 22:42 ` Chris Wright
2004-11-10 17:43 ` Jonathan Corbet
2004-11-10 19:32 ` Serge E. Hallyn
2004-11-04 23:08 ` [RFC] [PATCH] [3/6] LSM Stacking: capability LSM stacking support Serge Hallyn
2004-11-04 23:09 ` [RFC] [PATCH] [4/6] LSM Stacking: seclvl " Serge Hallyn
2004-11-04 23:11 ` [RFC] [PATCH] [5/6] LSM Stacking: SELinux " Serge Hallyn
2004-11-04 22:45 ` Chris Wright
2004-11-04 23:12 ` [RFC] [PATCH] [6/6] LSM Stacking: temporary setprocattr hack Serge Hallyn
2004-11-04 22:48 ` Chris Wright
2004-11-05 0:52 ` Serge E. Hallyn
2004-11-05 0:56 ` Chris Wright
2004-11-04 23:14 ` [RFC] [PATCH] [1/3] LSM Stacking: stackable bsdjail (tasklookup) Serge Hallyn
2004-11-04 23:15 ` [RFC] [PATCH] [2/3] LSM Stacking: stackable bsdjail (bsdjail lsm) Serge Hallyn
2004-11-04 23:16 ` [RFC] [PATCH] [3/3] LSM Stacking: stackable bsdjail (Documentation) Serge Hallyn
2004-11-04 23:51 ` [RFC] [PATCH] [0/6] LSM Stacking James Morris
2004-11-05 7:23 ` Valdis.Kletnieks
2004-11-05 16:32 ` Serge E. Hallyn
2004-11-05 16:51 ` Stephen Smalley
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=20041104145229.D2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.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®