STREAMS

In computer networking, STREAMS is the native framework in Unix System V for implementing character device drivers, network protocols, and inter-process communication. In this framework, a stream is a chain of coroutines that pass messages between a program and a device driver (or between a pair of programs). STREAMS originated in Version 8 Research Unix, as Streams (not capitalized).

STREAMS's design is a modular architecture for implementing full-duplex I/O between kernel and device drivers. Its most frequent uses have been in developing terminal I/O (line discipline) and networking subsystems. In System V Release 4, the entire terminal interface was reimplemented using STREAMS.^[1] An important concept in STREAMS is the ability to push drivers – custom code modules which can modify the functionality of a network interface or other device – together to form a stack. Several of these drivers can be chained together in order.

History

STREAMS was based on the Streams I/O subsystem introduced in the Eighth Edition Research Unix (V8) by Dennis Ritchie, where it was used for the terminal I/O subsystem and the Internet protocol suite. This version, not yet called STREAMS in capitals, fit the new functionality under the existing device I/O system calls (open, close, read, write, and ioctl),^[2] and its application was limited to terminal I/O and protocols providing pipe-like I/O semantics.

This I/O system was ported to System V Release 3 by Robert Israel, Gil McGrath, Dave Olander, Her-Daw Che, and Maury Bach as part of a wider framework intended to support a variety of transport protocols, including TCP, ISO Class 4 transport, SNA LU 6.2, and the AT&T NPACK protocol (used in RFS).^[3] It was first released with the Network Support Utilities (NSU) package of UNIX System V Release 3.^[4] This port added the putmsg, getmsg, and poll system calls, which are nearly equivalent in purpose to the send, recv, and select calls from Berkeley sockets. The putmsg and getmsg system calls were originally called send and recv,^[5] but were renamed to avoid namespace conflict.^[6] In System V Release 4, STREAMS was extended and used for the terminal I/O framework and pipes, providing useful new functionality like bidirectional pipes and file descriptor passing.^[3] A port for UNICOS was also produced. Eric S. Raymond quotes Ritchie as saying about the complexity of System V STREAMS when compared to his V8 Streams that "Streams means something different when shouted".^[7]

Concurrent with the System V Release 3 port, AT&T developed protocol-independent STREAMS message passing guidelines for the link,^[8] network,^[9] and transport layers^[10] of the OSI model (layers 2-4). Due to the typically close implementation coupling of the network and transport protocols in a given protocol stack, and the typical practice of implementing layers 5-7 outside of the kernel, only the link^[8] and transport layer^[11] STREAMS service interfaces were later standardized by X/Open. In conjunction with the transport message passing model, the Transport Layer Interface (later adopted as the X/Open Transport Interface) was defined to provide a transport protocol-independent API for application development. Also, a library supporting the session, presentation and application layers^[12] was defined and later standardized by The Open Group.^[13]

STREAMS was required for conformance with the Single UNIX Specification versions 1 (UNIX 95) and 2 (UNIX 98), but as a result of the refusal of the BSD and Linux developers to provide STREAMS,^{[citation needed]} was marked as optional for POSIX compliance by the Austin Group in version 3 (UNIX 03). POSIX.1-2008 with TC1 (IEEE Std 1003.1, 2013 edition) has designated STREAMS as 'marked obsolescent'^[14][15] meaning that said functionality may be removed in a future version of the specification. However, the specific definition of 'obsolescent' used^[16] also says that strictly conforming POSIX applications 'shall not use obsolescent features'.

Technical overview

Example use of Streams to implement remote command execution over a network, after (Ritchie 1984)

In Version 7 Unix, a command was connected to a terminal (keyboard and screen, or keyboard and printer) through a mechanism called the line discipline, which would buffer a single line of input, i.e., wait for the user to press the Return key before sending input to the program for processing; this allowed simple error correction. Streams replaced this with a set of processing modules organized in a linear chain that allowed bidirectional communication between neighboring modules. Programs could "push" a new module onto one end of the chain to change the behavior of a terminal or other character device. Ritchie gives the example chain of a terminal module chained with a Datakit network module to achieve remote login over a network.^[5] Aside from characters (bytes) going from program to device and vice versa, Streams could carry control messages such as "hangup" (drop connection) and ioctl messages.

Streams could also be used for inter-process communication, by connecting two processes to pseudoterminals. This functionality was implemented in the mpx window system for the Blit graphics terminal, which could display multiple terminal emulator windows. Each window was a process that communicated with the window system through a pseudoterminal that had the line discipline driver installed, sending typed characters to it and receiving text (and graphics) to display. Control signals designated the user's wish to switch between windows or close them.^{[17][18]:348–350}

The actual Streams modules live in kernel space on Unix, and are installed (pushed) and removed (popped) by the ioctl system call. For example, to install the aforementioned line discipline on a file descriptor fd referring to a terminal device, one would write (in C):^[18]:347

ioctl(fd, PUSH, TTYLD);

To perform input/output on a stream, one either uses the read and write system calls as with regular file descriptors, or a set of STREAMS-specific functions to send control messages.^[19]

Ritchie admitted to regretting having to implement Streams in the kernel, rather than as processes, but felt compelled to do so for reasons of efficiency.^[5] A later Plan 9 implementation did implement modules as user-level processes.^[20]

Implementations

STREAMS has mostly been used in the System V Unix world; however, other implementations exist:

• Plan 9 originally used a multi-processor variant of Research Unix's Streams. During the transition to the third edition of Plan 9, Streams were further simplified to simple I/O queues.^[20]
• An implementation written at Mentat was used in Novell NetWare for its TCP/IP stack, and licensed by Apple for use in the classic Mac OS starting in version 7.5.2, as part of the Open Transport networking system. (In macOS, the Classic Environment used the STREAMS architecture, but the native networking architecture uses the Berkeley sockets API and is derived from the BSD networking code.)
• FreeBSD has basic support for STREAMS-related system calls, as required by SVR4 binary compatibility layer.^[21]
• The Windows NT kernel offered a full port of STREAMS as the streams.sys binary. NT DDK even had a chapter on STREAMS, going as late as NT4 though in NT4 DDK it was declared obsolete. The original TCP/IP stack for Windows NT 3.1 was implemented atop STREAMS by Spider Systems, and used the streams.sys binary. From NT 3.5 up, TCP/IP was remade completely,^[22][23] by adopting the one from Microsoft LAN Manager for OS/2 1.x.^{[citation needed]}
• The AlphaTCP networking layer in AMOS, the operating system for Alpha Micro computers, was also based on SpiderStreams.^[24]

Linux does not include STREAMS functionality without third-party add-ons. Caldera had "pushed" for STREAMS to be included in Linux ca. 1998, to support its Netware for Linux, but it was rejected outright by the Linux kernel developers on technical grounds (mainly performance).^[25] The compatibility layers in Linux for other operating systems convert STREAMS operations into sockets as early as possible.^[26] The implementation used by Caldera was "LiS", by a company called GCOM; it later figured in the legal battles by Caldera's successor, the SCO Group, against Linux, with SCO claiming that Linux with STREAMS infringed what it believed to be its copyrights to System V.^[25]

Notes

References

• Goodheart, Berny; Cox, James (1994), The magic garden explained: the internals of UNIX System V Release 4, an open-systems design, Australia: Prentice Hall, ISBN 0-13-098138-9 
• Open Group (1999), "Transport Provider Interface (TPI) Specification", Open Group CAE Specification (Berkshire, UK: Open Group Publication) 
• Open Group (September 1993), "ACSE/Presentation Services API (XAP)", X/Open CAE Specification (Berkshire, UK: X/Open Company Limited) XAP (c303), ISBN 1-872630-91-X 
• Pajari, George (1992), Writing UNIX Device Drivers (2nd Printing, 1st ed.), Reading, MA: Addison-Wesley, ISBN 0-201-52374-4, https://archive.org/details/writingunixdevic00paja_0 
• Ritchie, Dennis M. (October 1984). "A Stream Input-Output System". AT&T Bell Laboratories Technical Journal (AT&T) 63 (8 Part 2): 1897–1910. doi:10.1002/j.1538-7305.1984.tb00071.x. https://www.bell-labs.com/usr/dmr/www/st.html. Retrieved 2018-01-13. 
• Stevens, W. Richard (1993), Advanced Programming in the UNIX Environment (15th Printing, 1st ed.), Reading, MA: Addison-Wesley, ISBN 0-201-56317-7, https://archive.org/details/advancedprogramm00stev 
• Thomas, Rebecca; Rogers, Lawrence R.; Yates, Jean L. (1986), Advanced Programmers Guide to UNIX System V, Berkeley, CA: Osborne McGraw-Hill, ISBN 0-07-881211-9 
• UNIX International (August 20, 1991), Data Link Provider Interface (DLPI) Specification, UNIX International Publication (Revision 2.0.0, Draft 2 ed.), Parsippany, N.J.: UNIX International Press, http://www.openss7.org/docs/dlpi.pdf, retrieved 2009-07-27 
• UNIX International (August 17, 1992), Network Provider Interface (NPI) Specification, UNIX International Publication (Revision 2.0.0, Draft 2 ed.), Parsippany, N.J.: UNIX International Press, http://www.openss7.org/docs/npi.pdf, retrieved 2009-07-27 
• UNIX International (December 10, 1992), Transport Provider Interface Specification, UNIX International Publication (Revision 1.5, Draft 2 ed.), Parsippany, N.J.: UNIX International Press, http://www.openss7.org/docs/tpi.pdf, retrieved 2009-07-27 
• UNIX International (October 25, 1990), ACSE/Presentation Library Interface (APLI) Specification, UNIX International Publication (Draft ed.), Parisppany, N.J.: UNIX International Press 
• Waite Group (1987), Mitchel Waite, ed., UNIX Papers (2nd Printing, 1st ed.), Indianapolis, IN: Howard W. Sams & Company, ISBN 0-672-22578-6, https://archive.org/details/unixpapers00wait 
• Barr, Adam (June 19, 2001), "Microsoft, TCP/IP, Open Source, and Licensing", Kuro5hin, http://www.kuro5hin.org/story/2001/6/19/05641/7357, retrieved February 22, 2013 
• Valentine, Mark (June 19, 2001). "Re: Query: How to tell if Microsoft is using BSD TCP/IP code?". freebsd-hackers (Mailing list). Retrieved February 22, 2013.

External links

• The original stream(4) manual from Unix 8th Edition
• The STREAMS framework in Digital UNIX – from the Digital UNIX Network Programmer's Guide
• Oracle (formerly, Sun) STREAMS Programming Guide

0.00 (0 votes) Original source: https://en.wikipedia.org/wiki/STREAMS. Read more