From: Dan C Marinescu <dan_c_marinescu@yahoo.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The price of SELinux (CPU)
Date: Mon, 3 Oct 2005 22:06:02 -0700 (PDT) [thread overview]
Message-ID: <20051004050602.10057.qmail@web35501.mail.mud.yahoo.com> (raw)
In-Reply-To: <43420C1B.3020607@comcast.net>
i suggested you to disable selinux in order to have
something to compare to... (engineers compare,
measure, instead of believing in rummors...)
d
--- John Richard Moser <nigelenki@comcast.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm not an abortionist; if I hear something has an
> ugly side, I try to
> find out if it can be fixed, and if the trade-off is
> worth getting rid
> of it. SELinux and LSM are quite useful you know;
> the overhead is
> probably not even that significant on the desktop to
> gamers (although if
> you TELL them about it they'll piss themselves),
> from a practical
> viewpoint considering their excessive hardware.
>
> Dan C Marinescu wrote:
> > try selinux=0, _if u feel that way :-)
> >
> > about big o:
> >
> >
>
http://www.maththinking.com/boat/compsciBooksIndex.html
> >
> > daniel
> >
> >
> >
> > --- John Richard Moser <nigelenki@comcast.net>
> wrote:
> >
> >
> > I've heard that SELinux has produced benchmarks
> such
> > as 7% increased CPU
> > load. Is this true and current? Is it dependent
> on
> > policy? What is
> > the policy lookup complexity ( O(1), O(n),
> > O(nlogn)...)? Are there
> > other places where a bottleneck may exist aside
> from
> > gruffing with the
> > policy? Isn't the policy actually in xattrs so
> it's
> > O(1)? Where else
> > would an overhead that big come from aside from a
> > lookup in a table?
> >
> > ....
> >
> > Why is the sky blue? Why do you have a mustach?
> > Why doesn't mommy have
> > one? Does she shave it?
> >
> > At any rate, my personal end goal is a secure
> > high-performance operating
> > system, as user friendly as Ubuntu, Mandriva, or
> > Win----. To this end,
> > I'm (still; a lot of you have seen me before)
> > evaluating the performance
> > hit of various user and kernel security
> enhancements
> > like PaX,
> > ProPolice, various OpenWall/GrSecurity niceness
> that
> > needs to be divided
> > out, and of course LSM/SELinux. Also wondering
> > about that PHKMalloc
> > thing on openbsd; is it really all that, is it
> junk,
> > how's it compare to
> > the recent ptmalloc work, and can it run on Linux
> > for direct benching .
> > . . but that's off topic.
> >
> > --
> > All content of all messages exchanged herein are
> > left in the
> > Public Domain, unless otherwise explicitly stated.
> >
> > Creative brains are a valuable, limited
> > resource. They shouldn't be
> > wasted on re-inventing the wheel when there
> are
> > so many fascinating
> > new problems waiting out there.
> >
> --
> > Eric Steven Raymond
> - -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> > __________________________________
> > Yahoo! Mail - PC Magazine Editors' Choice 2005
> > http://mail.yahoo.com
>
>
> - --
> All content of all messages exchanged herein are
> left in the
> Public Domain, unless otherwise explicitly stated.
>
> Creative brains are a valuable, limited
> resource. They shouldn't be
> wasted on re-inventing the wheel when there are
> so many fascinating
> new problems waiting out there.
> --
> Eric Steven Raymond
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird -
> http://enigmail.mozdev.org
>
>
iD8DBQFDQgwahDd4aOud5P8RArHEAJ9GFTpKPX3BbAR9vF/UCxeqbXO8DQCgi3sC
> R8bKVy1wxP2SiGJyc0MB4Xw=
> =vvMx
> -----END PGP SIGNATURE-----
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
next prev parent reply other threads:[~2005-10-04 5:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 4:28 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 [this message]
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
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=20051004050602.10057.qmail@web35501.mail.mud.yahoo.com \
--to=dan_c_marinescu@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome