From: serue@us.ibm.com
To: Chris Wright <chrisw@osdl.org>
Cc: serue@us.ibm.com, linux-kernel@vger.kernel.org,
Kurt Garloff <garloff@suse.de>,
Stephen Smalley <sds@epoch.ncsc.mil>,
linux-security-module@wirex.com
Subject: Re: [PATCH 0/5] LSM hook updates
Date: Fri, 26 Aug 2005 12:35:08 -0500 [thread overview]
Message-ID: <20050826173508.GA11489@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20050826164139.GK7762@shell0.pdx.osdl.net>
Quoting Chris Wright (chrisw@osdl.org):
> > A little surprising: kernbench is improved, but dbench and tbench
> > are worse - though within the 95% CI.
>
> It is interesting. Would be good to see what happens with the cap_ bits
> used in SELinux instead of secondary callout.
Here are the new numbers next to the originals. 'patchedv2' is
obviously with your new patch. Kernbench keeps getting faster :)
dbench (throughput, larger is better):
original: 357.957780 +/- 3.509188
patched: 351.266820 +/- 4.736168
patchedv2: 352.414880 +/- 3.649639
tbench (throughput, larger is better):
original: 38.710270 +/- 0.028970
patched: 38.210506 +/- 0.032954
patchedv2: 38.018038 +/- 0.024762
kernbench (time, smaller is better):
original: 91.837000 +/- 0.324471
patched: 91.466000 +/- 0.308797
patchedv2: 91.079000 +/- 0.236836
reaim (#children vs throughput, larger is better):
original:
1 48702.197000 1875.223996
3 131411.870000 4497.107969
5 130219.174000 6365.289551
7 162377.027000 3131.071134
9 155432.904000 4964.935291
11 169784.384000 4490.812272
13 164540.169000 3902.652904
15 172983.569000 3149.934591
patched:
1 47525.273000 1509.578035
3 132151.651000 2282.043786
5 131244.291000 5874.212092
7 165629.693000 4646.641230
9 156163.110000 3422.903849
11 170608.526000 4132.988693
13 164863.102000 3664.214481
15 172947.803000 2548.662380
patchedv2:
1 46796.702000 1454.752458
3 126771.430000 3296.287229
5 132779.408000 4786.218275
7 165525.949000 3364.383587
9 156160.772000 3358.822121
11 172681.856000 2524.954098
13 162618.395000 4892.710796
15 172982.170000 3105.761847
> Also, need to run ia64,
> do you have an ia64 box?
Not a one, I'm afraid.
-serge
next prev parent reply other threads:[~2005-08-26 17:36 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
2005-08-26 16:41 ` Chris Wright
2005-08-26 17:35 ` serue [this message]
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=20050826173508.GA11489@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®