> Rewriting SELinux to use whatever approach you devise would be a better > test, as it will exercise your methods from every hook and likely give > you a better sense as to both the correctness and performance overhead > of your approach. > > Plain spin_locks are not safe here, as your methods can be called from > hard irq or soft irq from certain hooks, and this will happen with > SELinux. Locking overhead is going to kill you here. I will start an RCU version and port SELinux to use the hashtable. thanks, -serge
This archive was generated by hypermail 2.1.3 : Wed Oct 27 2004 - 06:16:01 PDT