Lines Matching +full:multi +full:- +full:protocol

31 .\".ds RH "Socket/protocol interface
33 \s+2Socket/protocol interface\s0
37 protocol switch table.  The following requests to a protocol
41 #define	PRU_ATTACH	0	/* attach protocol */
42 #define	PRU_DETACH	1	/* detach protocol */
52 #define	PRU_CONTROL	11	/* control operations on protocol */
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
79 A non-zero return value gives a
85 When a protocol is bound to a socket (with the \fIsocket\fP
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
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
133 pending connections.  The protocol module should fill
144 The protocol may, at its discretion, deallocate any data
149 This request is made only if the protocol entry in the protocol
152 will be sent to the protocol module.  It may be used to trigger
158 PRU_SEND requests (a protocol may indicate that a single user
160 specifying the PR_ATOMIC flag in its protocol description).
161 The data to be sent is presented to the protocol as a list of
163 parameter.  The protocol is responsible for preserving the data
169 protocol should delete any existing association(s).
174 intercepted by the socket routines).  It allows protocol-specific
179 (note the non-standard calling convention).
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.
209 bound to it.  The address (with protocol specific format) is returned
215 be made to the protocol.  The address format (protocol specific) is
219 The protocol module is supplied two sockets and requested to
226 The following requests are used internally by the protocol modules
229 in tracing a protocol's operation (e.g. PRU_SLOWTIMO).
233 occurs in the protocol's \fIpr_fastimo\fP routine.  The \fIaddr\fP
238 occurs in the protocol's \fIpr_slowtimo\fP routine.  The \fIaddr\fP
242 This request is used in the protocol-protocol interface, not by the
243 routines.  It requests reception of data destined for the protocol and
247 This request allows a protocol to send data destined for another
248 protocol module, not a user.  The details of how data is marked
249 ``addressed to protocol'' instead of ``addressed to user'' are
250 left to the protocol modules.  No protocols currently use this facility.