public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Jones <tonyj@suse.de>
To: Kurt Garloff <garloff@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@osdl.org>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	James Morris <jmorris@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Steve Beattie <smb@wirex.com>
Subject: Re: [PATCH 3/3] Use conditional
Date: Sun, 3 Jul 2005 12:00:07 -0700	[thread overview]
Message-ID: <20050703190007.GA30292@immunix.com> (raw)
In-Reply-To: <20050703154405.GE11093@tpkurt.garloff.de>

On Sun, Jul 03, 2005 at 05:44:05PM +0200, Kurt Garloff wrote:

Agree with James, pls resend to linux-security-module@wirex.com.

The topic of replacing dummy (with capability) was discussed there
last week, in the context of stacker, but a common solution for both
cases would be needed.

Also, I was going to ask where 4/5 and 5/5 were :-)

If you are claiming a perf increase it would be nice to get an idea
what these patches were even though you believe most of the gain was
in patch #3.

Thanks

> Hi,
> 
> this optimizes the case where no LSM is loaded and the (new) default 
> 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).
> 
> Enjoy,
> -- 
> Kurt Garloff, Director SUSE Labs, Novell Inc.

> From: Kurt Garloff <garloff@suse.de>
> Subject: Replace indirect calls by a branch
> References: SUSE40217, SUSE39439
> 
> In the LSM stub collection, rather do a branch than an indirect
> call. Many of the functions called do only return 0 or do nothing
> for the default (capability) case.
> This is a fast-path optimization; a branch is faster than an
> indirect call, even more so if correctly predicted.
> This shows a >3% perf. increase in netperf -t TCP_RR benchmark on IA64.
> (More exactly: The benchmark was taken with the next two patches
>  applied as well, but I attribute the main effect to this patch.)
> 
> This is patch 3/5 of the LSM overhaul.

  parent reply	other threads:[~2005-07-03 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 15:44 [PATCH 3/3] Use conditional Kurt Garloff
2005-07-03 16:51 ` James Morris
2005-07-03 21:17   ` Kurt Garloff
2005-07-03 19:00 ` Tony Jones [this message]
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=20050703190007.GA30292@immunix.com \
    --to=tonyj@suse.de \
    --cc=chrisw@osdl.org \
    --cc=garloff@suse.de \
    --cc=gregkh@suse.de \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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