From: Stephen Smalley <sds@tycho.nsa.gov>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: Performance optimization of libsepol and the need for detailed policydb docs.
Date: Mon, 05 Mar 2012 14:53:01 -0500 [thread overview]
Message-ID: <1330977181.7184.10.camel@moss-pluto> (raw)
In-Reply-To: <CAGZ=bqKEXNiRp_4YZaTvYEm6JhhAdk0LunwYbgWtuMKWPPAiiA@mail.gmail.com>
On Fri, 2012-03-02 at 22:05 -0800, Kyle Moffett wrote:
> In the past (with my previous employer), I participated in some
> efforts to analyze the performance of libsepol and identified some
> low-hanging fruit in the form of incorrectly sized hash tables (EG: A
> hash table with 2 entries has equivalent performance to a linked list
> except with a lot of extra code on the front end), but we never were
> able to polish up patches for merging.
>
> I would like to potentially take on some of this work, but I'd really
> need to have some better documentation on the various binary policy
> formats (base policy, modules, and linked policy). Is there any
> existing documentation or should I just start by writing some?
Old, but possibly helpful as a starting point:
http://securityblog.org/brindle/2006/07/05/selinux-policy-module-primer/
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2012-03-05 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 6:05 Performance optimization of libsepol and the need for detailed policydb docs Kyle Moffett
2012-03-03 13:25 ` Daniel J Walsh
2012-03-05 15:52 ` James Carter
2012-03-05 19:53 ` Stephen Smalley [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=1330977181.7184.10.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=kyle@moffetthome.net \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.