> Comparing the complexity (size) of this code with the q-n-d hash tables
> which are currently used one does wonder how useful it all will be. The
> additional indirections are not needed with q-n-d hashes.
I guess this is the big issue -- will the code potentially be useful to
anyone else?
Any important hashing is likely to involve specialized techniques
(e.g. RCU, per-cpu and various lockless strategies), and likely not use
this library code.
> But if it doesn't significantly add to the overall selinux patch then I
> guess it makes sense.
It doesn't add anything really, just some minor cleanups to make it more
suitable for general use.
It is also possible that the SELinux code may be further refined for
performance and utilize specialized hashing/locking techniques which are
no longer accommodated by this generic hashtab code.
My feeling at the moment is that there is probably not a compelling case
to pull the hashtab code out of SELinux into a kernel library, although
many of the suggestions would be worth applying to the SELinux resident
version.
- James
-- James Morris <jmorris@intercode.com.au>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/