STREAMS has been kept out of the kernel because the internal structure
and device-driver interface are slow and bloated. Would there be the
same opposition to including the user-space interface?
By user-space interface I mean getpmsg, putpmsg, the streams ioctls,
and some /dev entries. It seems to me that it would be possible to
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
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.
Or so I would think. I'm not a kernel person. Is there something
obvious I've missed?
zw
-
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/