mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: serue@us.ibm.com
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: serue@us.ibm.com, Chris Wright <chrisw@osdl.org>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org,
	Kurt Garloff <garloff@suse.de>
Subject: Re: [PATCH 0/5] LSM hook updates
Date: Fri, 26 Aug 2005 05:30:51 -0500	[thread overview]
Message-ID: <20050826103051.GA1815@sergelap.austin.ibm.com> (raw)
In-Reply-To: <1125062879.5812.67.camel@moss-spartans.epoch.ncsc.mil>

Quoting Stephen Smalley (sds@epoch.ncsc.mil):
> On Fri, 2005-08-26 at 04:23 -0500, serue@us.ibm.com wrote:
> > Here are some numbers on a 4way x86 - PIII 700Mhz with 1G memory (hmm,
> > highmem not enabled).  I should hopefully have a 2way ppc available
> > later today for a pair of runs.
> > 
> > dbench and tbench were run 50 times each, kernbench and reaim 10 times
> > each.  Results are mean +/- 95% confidence half-interval.  Kernel had
> > selinux and capabilities compiled in.
> > 
> > A little surprising: kernbench is improved, but dbench and tbench
> > are worse - though within the 95% CI.
> 
> Might be interesting to roll in Chris' patch (sent separately to lsm and
> selinux list) for "remove selinux stacked ops" in place of your patch,
> as that will avoid the indirect call through the secondary_ops in
> SELinux.  At that point, you can also disable the capability module
> altogether, as SELinux will just directly use the built-in cap_
> functions from commoncap.

True - I'll start a new set of jobs and hopefully report back sunday or
monday.

thanks,
-serge

  reply	other threads:[~2005-08-26 14:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25  1:20 Chris Wright
2005-08-25  1:20 ` [PATCH 1/5] Use capabilities as default w/ and w/out CONFIG_SECURITY Chris Wright
2005-08-25  1:20 ` [PATCH 2/5] Rework stubs in security.h Chris Wright
2005-08-26 17:31   ` Tony Jones
2005-08-26 17:59     ` Chris Wright
2005-08-26 18:03       ` Tony Jones
2005-08-26 18:00     ` Stephen Smalley
2005-08-26 18:08       ` Chris Wright
2005-08-26 18:11       ` Tony Jones
2005-08-25  1:20 ` [PATCH 3/5] Call security hooks conditionally if the security_op is filled out Chris Wright
2005-08-25  8:50   ` Kurt Garloff
2005-08-25 16:24     ` Chris Wright
2005-08-25  1:20 ` [PATCH 4/5] Remove unnecessary default capability callbacks Chris Wright
2005-08-25  1:20 ` [PATCH 5/5] Remove unnecesary capability hooks in rootplug Chris Wright
2005-08-25 14:38   ` serue
2005-08-25 15:13     ` Stephen Smalley
2005-08-25 16:21       ` Chris Wright
2005-08-25 16:23         ` Stephen Smalley
2005-08-25 17:06           ` Chris Wright
2005-08-25 21:13             ` Chris Wright
2005-08-25 16:28         ` serue
2005-08-25 21:12     ` Chris Wright
2005-08-31  6:34   ` Greg KH
2005-08-31 15:09     ` Chris Wright
2005-08-25  4:39 ` [PATCH 0/5] LSM hook updates James Morris
2005-08-25  5:32   ` Chris Wright
2005-08-25 19:15     ` Chris Wright
2005-08-26  9:23       ` serue
2005-08-26 13:27         ` Stephen Smalley
2005-08-26 10:30           ` serue [this message]
2005-08-26 16:41         ` Chris Wright
2005-08-26 17:35           ` serue
2005-08-26 17:49             ` Chris Wright
2005-08-25  9:52 ` serue
2005-08-25 10:18   ` serue
2005-08-25 16:19     ` Chris Wright

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=20050826103051.GA1815@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=chrisw@osdl.org \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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

all inboxes | Powered by JetHome®