From: Ondrej Oprala <ooprala@redhat.com>
To: Eric Paris <eparis@parisplace.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: setfscreatecon optimizations
Date: Wed, 09 Jan 2013 21:17:05 +0100 [thread overview]
Message-ID: <50EDD041.70505@redhat.com> (raw)
In-Reply-To: <CACLa4pur4DFPnuj-v10DPuBQ4hDqnV0gb02zR0-+ORwiT67CFQ@mail.gmail.com>
Fantastic :) thank you very much.
On 01/09/2013 03:51 PM, Eric Paris wrote:
> Something like the attached?
>
> On Wed, Jan 9, 2013 at 9:30 AM, Eric Paris <eparis@parisplace.org> wrote:
>> On Wed, Jan 9, 2013 at 7:03 AM, Ondrej Oprala <ooprala@redhat.com> wrote:
>>> Thank you for the pointers, it helped me out a lot. I tested the patched
>>> libselinux with
>>> $cp -a dir1 dir2
>>> and got an approx. 20% save in instruction count. The patch is attached.
>>> Thanks,
>> Thanks! I'm working on it right now. You did the:
>> __selinux_once(once, init_procattr);
>> init_thread_destructor();
>> Before variable declaration and you do not handle context==NULL, which
>> is how you clear the value. I'll fix both of those up and apply to
>> the devel tree. Thanks so much!
--
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.
next prev parent reply other threads:[~2013-01-09 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 13:20 setfscreatecon optimizations Ondrej Oprala
2013-01-08 14:48 ` Stephen Smalley
2013-01-09 12:03 ` Ondrej Oprala
2013-01-09 14:30 ` Eric Paris
2013-01-09 14:51 ` Eric Paris
2013-01-09 20:17 ` Ondrej Oprala [this message]
2013-01-09 21:30 ` Daniel J Walsh
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=50EDD041.70505@redhat.com \
--to=ooprala@redhat.com \
--cc=eparis@parisplace.org \
--cc=sds@tycho.nsa.gov \
--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.