What you put in user space doesnt really matter. Its completely outside
the kernel and it has no impact on performance of other code or maintenance
impact (except yours)
> implement these as a thin layer on top of the existing network and
> terminal code. Pushable modules can be faked: for example, pushing the
> tty module could either do nothing or fail depending on whether the fd
iBCS2 already does most of this sort of game in its SCO emulation in
kernel space - using these sort of techniques.
> in question is already a tty. If done right this thin layer should
> impose no performance penalty on code that doesn't use it, and should
> not interfere with future improvements in the kernel.
I question if you need it. The only non-protocol stack use of streams tends
to be TLI. Alexey Kuznetsov has a user space TLI emulation layer for linux
if someone wants to beat it back into shape
-
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/