I did think that an O/S is a thing that run application programs. If
applications want STREAMS, then we must provide them STREAMS.
You seem to think they must be in the kernel, nothing stops you from
doing a userland implementation of SysV streams. Everyone first says,
"Put this in the kernel.", very few people ask "Can we do this in
userspace?".
User programs don't care where the interfaces are actually
implemented, they just call functions and expect them to act a certain
way. OS designers and architects do care where it is implemented.
All conventional wisdom in the system design community says "STREAMS
are bad in the kernel", over and over. So work on a userland
implementation, or live without streams. The argument of "everybody
wants it" is never a good argument to put bad ideas into the kernel.
The one advantage of Linux is that we can filter what goes into the
kernel on technical merit alone, not what marketing or whatever
wants.
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu