From: Kurt Garloff <garloff@suse.de>
To: James Morris <jmorris@redhat.com>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Greg Kroah-Hartman <gregkh@suse.de>,
Steve Beattie <smb@wirex.com>,
linux-security-module@wirex.com
Subject: Re: [PATCH 3/3] Use conditional
Date: Sun, 3 Jul 2005 23:17:32 +0200 [thread overview]
Message-ID: <20050703211732.GG11093@tpkurt.garloff.de> (raw)
In-Reply-To: <Xine.LNX.4.44.0507031250290.30007-100000@thoron.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Hi James,
[added linux-security-module@wirex.com to Cc]
On Sun, Jul 03, 2005 at 12:51:20PM -0400, James Morris wrote:
> On Sun, 3 Jul 2005, Kurt Garloff wrote:
>
> > capablities is used. These are not called via indirect calls but
> > called as hardcoded calls and might thus be inlined; the price for
> > this is a conditional -- benchmarks done by hp showed this to be
> > beneficial (on ia64).
>
> What about on i386, x86_64 or ppc64?
We tested on i386 as well at the time, and it looked like a tiny
improvement. But doing the statistics, it was in the noise.
I have no numbers for x86_64 or ppc64.
If you have reason to believe that there could be regressions, we
should indeed do the benchmarks.
Sidenote: The patches 1 -- 2b alone still make sense, so I would
vote not for delaying their inclusion until we can collect numbers
for all arches we care about to take a decision on patch 3.
Best,
--
Kurt Garloff, Director SUSE Labs, Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-03 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 15:44 Kurt Garloff
2005-07-03 16:51 ` James Morris
2005-07-03 21:17 ` Kurt Garloff [this message]
2005-07-03 19:00 ` Tony Jones
2005-07-04 6:59 ` Kurt Garloff
2005-07-04 7:44 ` Tony Jones
2005-07-04 12:01 ` serge
2005-07-04 12:08 ` Kurt Garloff
2005-07-04 12:37 ` serge
2005-07-04 13:31 ` Kurt Garloff
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=20050703211732.GG11093@tpkurt.garloff.de \
--to=garloff@suse.de \
--cc=chrisw@osdl.org \
--cc=gregkh@suse.de \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=smb@wirex.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®