From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: Converting ebitmaps to copy-on-write?
Date: Wed, 26 Jul 2006 11:22:50 -0400 [thread overview]
Message-ID: <44C788CA.8040907@hp.com> (raw)
Can anyone think of reason why converting the ebitmap code to a copy on
write scheme would be a bad idea? Yes, there would be some overhead in
maintaining reference counts but I suspect the added overhead would be
more than offset by the reduction in kmalloc() calls ... thoughts?
--
paul moore
linux security @ hp
--
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 reply other threads:[~2006-07-26 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 15:22 Paul Moore [this message]
2006-07-27 15:38 ` Converting ebitmaps to copy-on-write? Karl MacMillan
2006-07-27 16:37 ` Paul Moore
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=44C788CA.8040907@hp.com \
--to=paul.moore@hp.com \
--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.