Lines Matching +full:system +full:- +full:on +full:- +full:module
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
38 module are possible:
52 #define PRU_CONTROL 11 /* control operations on protocol */
65 A call on the user request routine is of the form,
73 The address \fIaddr\fP is supplied for address-oriented requests
76 chain containing user-specified capabilities (see the \fIsendmsg\fP
77 and \fIrecvmsg\fP system calls). The protocol is responsible for
78 disposal of the data mbuf chains on output operations.
79 A non-zero return value gives a
86 system call) the protocol module is called with this
87 request. It is the responsibility of the protocol module to
95 at the time a socket is deleted. The protocol module may
101 an existing socket. The protocol module must verify that the
106 for incoming connection requests on the associated socket.
107 The protocol module should perform any state changes needed
115 may vary depending on the protocol. Virtual circuit protocols,
121 If a protocol supports the notion of \fImulti-casting\fP, it
122 is possible to use multiple connects to establish a multi-cast
132 has accepted the first connection on the queue of
133 pending connections. The protocol module should fill
143 the shutdown, as encoded in the \fIsoshutdown\fP system call).
152 will be sent to the protocol module. It may be used to trigger
173 UNIX \fIioctl\fP system call on a socket (and the ioctl is not
174 intercepted by the socket routines). It allows protocol-specific
179 (note the non-standard calling convention).
185 system call on a socket; it requests status of the associated socket.
188 optimal transfer size for the connection (based on buffer size,
194 Any ``out-of-band'' data presently available is to be returned. An
195 mbuf is passed to the protocol module, and the protocol
199 An error may be returned if out-of-band data is not (yet) available
205 Like PRU_SEND, but for out-of-band data.
219 The protocol module is supplied two sockets and requested to
224 system call.
242 This request is used in the protocol-protocol interface, not by the
248 protocol module, not a user. The details of how data is marked