JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
STREAMS Programming Guide
search filter icon
search icon

Document Information

Preface

Part I Application Programming Interface

1.  Overview of STREAMS

2.  STREAMS Application-Level Components

3.  STREAMS Application-Level Mechanisms

4.  Application Access to the STREAMS Driver and Module Interfaces

5.  STREAMS Administration

6.  Pipes and Queues

Part II Kernel Interface

7.  STREAMS Framework - Kernel Level

8.  STREAMS Kernel-Level Mechanisms

9.  STREAMS Drivers

10.  STREAMS Modules

11.  Configuring STREAMS Drivers and Modules

12.  Multithreaded STREAMS

13.  STREAMS Multiplex Drivers

Part III Advanced Topics

14.  Debugging STREAMS-based Applications

Part IV Appendixes

A.  Message Types

Ordinary Messages

M_BREAK

M_CTL

M_DATA

M_DELAY

M_IOCTL

M_PASSFP

M_PROTO

M_RSE

M_SETOPTS

M_SIG

High-Priority Messages

M_COPYIN

M_COPYOUT

M_ERROR

M_FLUSH

M_HANGUP

M_IOCACK

M_IOCDATA

M_IOCNAK

M_PCPROTO

M_PCRSE

M_PCSIG

M_READ

SO_MREADOFF and M_STOP

SO_MREADOFFI and M_STOPI

M_UNHANGUP

B.  Kernel Utility Interface Summary

C.  STREAMS-Based Terminal Subsystem

D.  STREAMS FAQ

Glossary

Index

Appendix A

Message Types

STREAMS message types differ in their intended purposes, their treatment at the stream head, and their message-queueing priority.

STREAMS does not prevent a module or driver from generating any message type and sending it in any direction on the stream. However, established processing and direction rules should be observed. Stream head processing according to message type is fixed, although certain parameters can be altered.