mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <hallyn@cs.wm.edu>
To: Chris Wright <chrisw@osdl.org>
Cc: John Richard Moser <nigelenki@comcast.net>,
	linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: LSM hooks
Date: Thu, 31 Mar 2005 22:34:52 -0500	[thread overview]
Message-ID: <20050401033452.GA16549@escher.cs.wm.edu> (raw)
In-Reply-To: <20050331062843.GR28536@shell0.pdx.osdl.net>

Quoting Chris Wright (chrisw@osdl.org):
> * John Richard Moser (nigelenki@comcast.net) wrote:
> > So, Which version of Linux will first implement stacking in LSM as per
> > Serge Hallyn's patches?
> 
> None are ready yet.  Serge is still wading through performance testing.
> There's no telling about merging without a magic eightball, a handle on
> the performance issues, and some bonafide users.

Oh, just to keep anyone interested up to date:  It turns out nearly all
of the inordinate performance degredation I was seeing in the last set
of results which I reported was due to a prefetch weirdness on my ppc64
test system.  In particular, the hlist_for_each_entry macro automatically
prefetches tmp->next.  Since my tests were done with selinux+capability,
it was the case that tmp->next was always NULL (which always causes a
bad prefetch case on ppc64) and, to boot, never used, since the
comparison inside the loop always succeeded and immediately returned
the first entry.

A new set of results should hopefully be coming next week.

-serge

      parent reply	other threads:[~2005-04-01  3:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  4:13 John Richard Moser
2005-03-31  5:59 ` Greg KH
2005-03-31  6:28 ` Chris Wright
2005-03-31  7:30   ` John Richard Moser
2005-04-01  3:34   ` Serge E. Hallyn [this message]

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=20050401033452.GA16549@escher.cs.wm.edu \
    --to=hallyn@cs.wm.edu \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=nigelenki@comcast.net \
    /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®