public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Dan C Marinescu <dan_c_marinescu@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The price of SELinux (CPU)
Date: Tue, 04 Oct 2005 16:36:06 -0400	[thread overview]
Message-ID: <4342E7B6.7050500@tmr.com> (raw)
In-Reply-To: <20051004070609.18835.qmail@web35504.mail.mud.yahoo.com>

Dan C Marinescu wrote:
> the benchmark "results" _look_ like being authored by
> some qa engineers... or sysadmins or something...
> 
> *** only a deep/intimate knowledge of kernel and fs
> and acl implementation details and many other areas
> could suggest a credible conclusion (most likely
> without even needing any "profiling" at all... on pure
> theoretical basis, mostly because you would know what
> goes where and when and how and why and how much it
> adds here and there, etc, etc, etc)

Any results not based on actual measurement are called "guesses" rather 
than "data." Such deep knowlege is useful to determine what to measure, 
not what you would measure if you thought it were necessary.

The measurements are very useful, in that they show the magnitude of the 
performance impact using a benchmark which was constructed to emulate 
certain real world loads. Since no one number or even series of numbers 
can fully describe what *will* happen, but these numbers show what 
*could* happen.
> 
> and i personally have a strong doubt that if the cpu
> activity was statistically increased with 7% for the
> very same elementary I/O, linus would have accepted
> this degradation... my $0.02... :-)

For some applications the issue isn't how fast the O/S runs, but if it 
is secure enough to be run at all. Given the speed of even commodity 
computers, it's probable that even a 2:1 slowdown would still result in 
useful operation, compared to doing the work without a computer.

I can't speak for Linus' thinking of course, but I have worked in secure 
environments before, both DOD and DOE, and information control is vital.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-10-04 20:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04  4:28 The price of SELinux (CPU) John Richard Moser
2005-10-04  4:38 ` Dan C Marinescu
2005-10-04  4:59   ` John Richard Moser
2005-10-04  5:06     ` Dan C Marinescu
2005-10-04  6:20       ` John Richard Moser
2005-10-04  6:39         ` Dan C Marinescu
2005-10-04  6:43         ` Dan C Marinescu
2005-10-04  6:51         ` Dan C Marinescu
2005-10-04 13:57           ` serue
2005-10-04  6:57         ` Dan C Marinescu
2005-10-04  7:06         ` Dan C Marinescu
2005-10-04 20:36           ` Bill Davidsen [this message]
2005-10-04 22:24             ` Dan C Marinescu
2005-10-04  5:03 ` Dan C Marinescu
2005-10-04 14:34 ` James Morris
2005-10-04 15:39 ` Valdis.Kletnieks
2005-10-04 18:29   ` John Richard Moser
2005-10-04 19:43     ` Valdis.Kletnieks
2005-10-04 20:10       ` John Richard Moser
2005-10-04 22:32         ` Valdis.Kletnieks
2005-10-04 23:00           ` Dan C Marinescu
2005-10-05  2:02           ` John Richard Moser
2005-10-05 19:42           ` Bill Davidsen
2005-10-05 19:40       ` Bill Davidsen

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=4342E7B6.7050500@tmr.com \
    --to=davidsen@tmr.com \
    --cc=dan_c_marinescu@yahoo.com \
    --cc=linux-kernel@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