From: Chris Wright <chrisw@osdl.org>
To: keith <kmannth@us.ibm.com>
Cc: devnull@us.ibm.com, djwong <djwong@us.ibm.com>,
Chris McDermott <lcm@us.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: SELinux performance issue with large systems (32 cpus)
Date: Tue, 23 Nov 2004 12:52:12 -0800 [thread overview]
Message-ID: <20041123125212.E14339@build.pdx.osdl.net> (raw)
In-Reply-To: <1101237725.27848.301.camel@knk>; from kmannth@us.ibm.com on Tue, Nov 23, 2004 at 11:22:05AM -0800
* keith (kmannth@us.ibm.com) wrote:
> I work with i386 16-way systems. When hyperthreading is enabled they
> have 32 "cpus". I recently did a quick performance check on with 2.6
> (as it turn out with a SElinux enabled) doing kernel builds.
Have you tried any recent -mm kernel? avc_lock was refactored to RCU
locking, and benchmarks shows it scales quite nicely now.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-11-23 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 19:22 SELinux performance issue with large systems (32 cpus) keith
2004-11-23 20:52 ` Chris Wright [this message]
2004-11-23 21:59 ` keith
2004-11-23 20:54 ` Stephen Smalley
2004-11-23 20:56 ` Valdis.Kletnieks
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=20041123125212.E14339@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=devnull@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.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