* Converting ebitmaps to copy-on-write?
@ 2006-07-26 15:22 Paul Moore
2006-07-27 15:38 ` Karl MacMillan
0 siblings, 1 reply; 3+ messages in thread
From: Paul Moore @ 2006-07-26 15:22 UTC (permalink / raw)
To: selinux
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Converting ebitmaps to copy-on-write?
2006-07-26 15:22 Converting ebitmaps to copy-on-write? Paul Moore
@ 2006-07-27 15:38 ` Karl MacMillan
2006-07-27 16:37 ` Paul Moore
0 siblings, 1 reply; 3+ messages in thread
From: Karl MacMillan @ 2006-07-27 15:38 UTC (permalink / raw)
To: Paul Moore; +Cc: selinux
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Converting ebitmaps to copy-on-write?
2006-07-27 15:38 ` Karl MacMillan
@ 2006-07-27 16:37 ` Paul Moore
0 siblings, 0 replies; 3+ messages in thread
From: Paul Moore @ 2006-07-27 16:37 UTC (permalink / raw)
To: Karl MacMillan; +Cc: selinux
Karl MacMillan wrote:
> 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.
Stephen Smalley and I had a discussion off list about this and came to a
solution that addresses my concerns (performance for the NetLabel/CIPSO
patch).
--
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-07-27 16:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-26 15:22 Converting ebitmaps to copy-on-write? Paul Moore
2006-07-27 15:38 ` Karl MacMillan
2006-07-27 16:37 ` Paul Moore
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.