| Skip Navigation Links | |
| Exit Print View | |
|
STREAMS Programming Guide |
Part I Application Programming Interface
2. STREAMS Application-Level Components
3. STREAMS Application-Level Mechanisms
4. Application Access to the STREAMS Driver and Module Interfaces
7. STREAMS Framework - Kernel Level
8. STREAMS Kernel-Level Mechanisms
11. Configuring STREAMS Drivers and Modules
Routing Data Through a Multiplexer
Connecting And Disconnecting Lower Streams
Multiplexer Construction Example
Upper Write put Procedure Sample
Upper Write service Procedure Sample
14. Debugging STREAMS-based Applications
B. Kernel Utility Interface Summary
The following are general multiplexer design guidelines:
The upper half of the multiplexer acts like the end of the upper stream. The lower half of the multiplexer acts like the head of the lower stream. Service procedures are used for flow control.
Message routing is based on multiplexer-specific criteria.
When one stream is being fed by many streams, flow control may have to take place. Then all feeding streams on the other end of the multiplexer have to be enabled when the flow control is relieved.
When one stream is feeding many streams, flow control may also have to take place. Be careful not to starve other streams when one becomes flow controlled.
Upper and lower multiplexers share the same perimeter type and concurrency level. (See MT STREAMS Perimeters for information about perimeters.)
|