From: James Morris <jmorris@namei.org>
To: Joy Latten <latten@austin.ibm.com>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: SELinux performance
Date: Wed, 14 Dec 2005 19:47:33 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.63.0512141946090.21033@excalibur.intercode> (raw)
In-Reply-To: <1134590934.2630.207.camel@faith.austin.ibm.com>
On Wed, 14 Dec 2005, Joy Latten wrote:
> A while back I took up some SELinux performance work that a colleague of
> mine, Kylie Hall had done. The patch added ipv4 address, ipv6 address
> and port caches to SELinux. I believe I sent the patch a while back
> also, but can do so again if anyone is interested. The caches are
> exercised in such SELinux hooks as socket_bind(), socket_connect() and
> socket_sock_rcv_skb(). Bandwidth has allowed me some time to work on
> this. Can anyone recommend a benchmark that will exercise this code? I
> figured something that utilized many ip addresses or ports.
apachebench is a good basic test, and you can also try webstone, lmbench
and iperf.
Not sure how to realistically simulate large numbers of IP addresses.
- James
--
James Morris
<jmorris@namei.org>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-12-15 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 20:08 SELinux performance Joy Latten
2005-12-15 0:47 ` James Morris [this message]
2005-12-15 1:31 ` sharp
2005-12-15 4:37 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2007-07-01 7:20 selinux performance somayeh afzali
2007-07-01 13:51 ` James Morris
2007-07-04 21:38 ` Steve G
2007-07-04 11:20 somayeh afzali
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.63.0512141946090.21033@excalibur.intercode \
--to=jmorris@namei.org \
--cc=latten@austin.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.