linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: LSM performance measurement
Date: Thu, 7 Jul 2022 11:54:00 +0300	[thread overview]
Message-ID: <CACE9dm-uGHEK7NuQ35CR+MhhB9z2Nw0W0SgttRL7qzohi9Egqw@mail.gmail.com> (raw)
In-Reply-To: <f871c6ad-0fa1-1c4a-bf7c-47070abce444@schaufler-ca.com>

Hi Casey,

Thanks. Those certainly sound familiar..
Will have a look.

-Dmitry

On Wed, Jul 6, 2022 at 6:39 PM Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> On 7/6/2022 8:22 AM, Dmitry Kasatkin wrote:
> > Hi,
> >
> > Could anybody suggest a good approach/test suite to measure LSMs
> > runtime overheads?
>
> I have used LMbench, ltp and kernel builds when checking the
> overhead on the LSM stacking work. I have also tried timing the
> SELinux, audit and Smack testsuites, but they all have built in
> delays that make performance numbers questionable. Be sure to
> include network throughput and latency measurements if you're
> looking at SELinux and/or Smack. Also be sure that you have
> meaningful policy loaded, that you're consistent with how IMA
> is used, and that you know how your audit limits are configured.
>


-- 
Thanks,
Dmitry

  reply	other threads:[~2022-07-07  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 15:22 LSM performance measurement Dmitry Kasatkin
2022-07-06 15:39 ` Casey Schaufler
2022-07-07  8:54   ` Dmitry Kasatkin [this message]
2022-07-06 15:47 ` Igor Zhbanov
2022-07-07  8:54   ` Dmitry Kasatkin

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=CACE9dm-uGHEK7NuQ35CR+MhhB9z2Nw0W0SgttRL7qzohi9Egqw@mail.gmail.com \
    --to=dmitry.kasatkin@gmail.com \
    --cc=casey@schaufler-ca.com \
    --cc=linux-security-module@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).