Perhaps the kernel could treat UDI like it treats STREAMS - not
included in the kernel sources proper, but has the hooks to
accommodate the UDI framework as a loadable module? So UDI
would be available to those with a distinct need, but not the
officially sanctioned "Linux Way (tm)".
As best I can tell, the only STREAMS-specific hooks provided
by the kernel are the {get,put}pmsg() syscall table entries -
the couple other changes were things that made just sense to
do, with or without STREAMS. UDI would probably not even need
this (syscall) level of kernel/user UDI-specific accommodation.
Accommodation (not inclusion) of a loadable UDI framework by the
kernel could similarly be "earned" by the UDI piece by its using
only extant kernel facilities, or by persuading acceptance of any
needed additional facilities on the basis of general merit (as
opposed to saying "This has to be in to support UDI"). Added
hooks would have to stand on their own merit.
...jfree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/