Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

streamtab(9s) [bsd man page]

streamtab(9S)						    Data Structures for Drivers 					     streamtab(9S)

NAME
streamtab - STREAMS entity declaration structure SYNOPSIS
#include <sys/stream.h> INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). DESCRIPTION
Each STREAMS driver or module must have a streamtab structure. streamtab is made up of qinit structures for both the read and write queue portions of each module or driver. Multiplexing drivers require both upper and lower qinit structures. The qinit structure contains the entry points through which the module or driver routines are called. Normally, the read QUEUE contains the open and close routines. Both the read and write queue can contain put and service procedures. STRUCTURE MEMBERS
struct qinit *st_rdinit; /* read QUEUE */ struct qinit *st_wrinit; /* write QUEUE */ struct qinit *st_muxrinit; /* lower read QUEUE*/ struct qinit *st_muxwinit; /* lower write QUEUE*/ SEE ALSO
qinit(9S) STREAMS Programming Guide SunOS 5.10 11 Apr 1991 streamtab(9S)

Check Out this Related Man Page

queue(9S)						    Data Structures for Drivers 						 queue(9S)

NAME
queue - STREAMS queue structure SYNOPSIS
#include <sys/stream.h> INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI) DESCRIPTION
A STREAMS driver or module consists of two queue structures, one for upstream processing (read) and one for downstream processing (write). This structure is the major building block of a stream. It contains pointers to the processing procedures, pointers to the next and previous queues in the stream, flow control parameters, and a pointer defining the position of its messages on the STREAMS scheduler list. The queue structure is defined as type queue_t. STRUCTURE MEMBERS
struct qinit*q_qinfo; /* module or driver entry points */ struct msgb*q_first; /* first message in queue */ struct msgb*q_last; /* last message in queue */ struct queue*q_next; /* next queue in stream */ struct queue*q_link; /* to next queue for scheduling*/ void *q_ptr; /* pointer to private data structure */ size_t q_count; /* approximate size of message queue */ uint_t q_flag; /* status of queue */ ssize_t q_minpsz; /* smallest packet accepted by QUEUE*/ ssize_t q_maxpsz; /*largest packet accepted by QUEUE */ size_t q_hiwat; /* high water mark */ size_t q_lowat; /* low water mark */ Valid flags are as follows: QENAB Queue is already enabled to run. QWANTR Someone wants to read queue. QWANTW Someone wants to write to queue. QFULL Queue is considered full. QREADR This is the reader (first) queue. QUSE This queue is in use (allocation). QNOENB Do not enable queue by way of putq(). SEE ALSO
strqget(9F), strqset(9F), module_info(9S), msgb(9S), qinit(9S), streamtab(9S) Writing Device Drivers STREAMS Programming Guide SunOS 5.10 12 Nov 1996 queue(9S)
Man Page

2 More Discussions You Might Find Interesting

1. Programming

Entry Points Routine

How do we pronounciate bdevsw and cdevsw Kernel resources ? I presume it as block or charcter device software table. Am I Correct in my assumption ? Thanks in advance. (9 Replies)
Discussion started by: S.P.Prasad
9 Replies

2. AIX

AIX STREAMS driver question

Hi all, I have a AIX kernel STREAMS question need your help, I need to implement a firewall on AIX and get packet raw data then decide pass or drop it, I've seen similiar firewall code on HP-UX, on HP-UX, you have to implement a "dlpi STREAMS driver", and specify it as a "dlpi" driver in... (1 Reply)
Discussion started by: rocktilldie
1 Replies

Featured Tech Videos