qinit(9s) [freebsd man page]

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

NAME

       qinit - STREAMS queue processing procedures structure

SYNOPSIS

       #include <sys/stream.h>

INTERFACE LEVEL

       Architecture independent level 1 (DDI/DKI)

DESCRIPTION

       The   qinit  structure  contains  pointers to processing procedures for a  QUEUE. The streamtab structure for the module or driver contains
       pointers to one queue(9S) structure for both upstream and downstream processing.

STRUCTURE MEMBERS

       int		   (*qi_putp)();      /* put procedure */
       int		   (*qi_srvp)();      /* service procedure */
       int		   (*qi_qopen)();     /* open procedure */
       int		   (*qi_qclose)();    /* close procedure */
       int		   (*qi_qadmin)();    /* unused */
       struct module_info  *qi_minfo;	      /* module parameters */
       struct module_stat  *qi_mstat;	      /* module statistics */

SEE ALSO

       queue(9S), streamtab(9S)

       Writing Device Drivers

       STREAMS Programming Guide

NOTES

       This release includes no support for module statistics.

SunOS 5.10							    11 Apr 1991 							 qinit(9S)

put(9F) 						   Kernel Functions for Drivers 						   put(9F)

NAME

       put - call a STREAMS put procedure

SYNOPSIS

       #include <sys/stream.h>
       #include <sys/ddi.h>

       void put(queue_t *q, mblk_t *mp);

INTERFACE LEVEL

       Architecture independent level 1 (DDI/DKI).

PARAMETERS

       q      Pointer to a STREAMS queue.

       mp     Pointer to message block being passed into queue.

DESCRIPTION

       put()  calls the put procedure ( put(9E) entry point) for the STREAMS queue specified by q, passing it the message block referred to by mp.
       It is typically used by a driver or module to call its own put procedure.

CONTEXT

       put() can be called from a STREAMS module or driver put or service routine, or from an associated interrupt handler, timeout,  bufcall,	or
       esballoc call-back. In the latter cases, the calling code must guarantee the validity of the q argument.

       Since  put()  may cause re-entry of the module (as it is intended to do), mutexes or other locks should not be held across calls to it, due
       to the risk of single-party deadlock (put(9E), putnext(9F), putctl(9F), qreply(9F)). This function is  provided	as  a  DDI/DKI	conforming
       replacement for a direct call to a put procedure.

SEE ALSO

       put(9E), freezestr(9F), putctl(9F), putctl1(9F), putnext(9F), putnextctl(9F), putnextctl1(9F), qprocson(9F), qreply(9F)

       Writing Device Drivers

	STREAMS Programming Guide

NOTES

       The caller cannot have the stream frozen when calling this function. See  freezestr(9F).

       DDI/DKI	conforming  modules  and  drivers  are	no longer permitted to call put procedures directly, but must call through the appropriate
       STREAMS utility function, for example, put(9E), putnext(9F), putctl(9F), and qreply(9F). This function is provided as a DDI/DKI	conforming
       replacement for a direct call to a put procedure.

       The put() and putnext() functions should be called only after qprocson() is finished.

SunOS 5.11							    28 Apr 1992 							   put(9F)