From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Paul Moore <paul.moore@hp.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Converting ebitmaps to copy-on-write?
Date: Thu, 27 Jul 2006 11:38:50 -0400 [thread overview]
Message-ID: <44C8DE0A.1080400@mentalrootkit.com> (raw)
In-Reply-To: <44C788CA.8040907@hp.com>
Paul Moore wrote:
> 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?
>
>
Which ebitmaps are shared enough for this to help? I don't think I have
enough context to know whether this would be a good idea or not.
Karl
--
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:[~2006-07-27 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 15:22 Converting ebitmaps to copy-on-write? Paul Moore
2006-07-27 15:38 ` Karl MacMillan [this message]
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=44C8DE0A.1080400@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=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.