Lines Matching +full:control +full:- +full:field

57 Additionally, users can specify a particular stack to use on a per-connection
81 de-registers the function block.
88 field.
93 field.
98 field by explicitly providing that name.
161 .Bd -literal -offset indent
193 field identifies the unique name of the TCP stack, and should be no longer than
194 TCP_FUNCTION_NAME_LEN_MAX-1 characters in length.
208 Each of these function pointers must be non-NULL.
211 stack (or, when the socket is first opened), it should set a non-NULL
214 field.
216 TCP stack (or, when the socket is closed), it should set a non-NULL pointer
219 field.
223 argument is non-NULL, the function to which it points is called when the
224 kernel is destroying the TCP control block or when the socket is transitioning
226 The function is called with arguments of the TCP control block and an integer
229 or one if the TCP control block is being destroyed.
232 non-NULL pointer in the
258 timer fires by setting a non-NULL function pointer in the
260 field.
264 TCP control block in a valid state for the remainder of the retransmit
270 field must be non-NULL.
274 field.
278 if this function pointer is non-NULL and finally perform the stack switch.
291 TCP control block, the TCP stack can initialize its own per-connection storage.
294 field in the
296 control block structure has been reserved to hold a pointer to this
297 per-connection storage.
305 function to initialize this field.
313 update all fields in the TCP control block to the greatest extent practical.
321 functions return zero on success and non-zero on failure.
338 .Bl -tag -width Er
354 .Bl -tag -width Er
363 .Bl -tag -width Er
367 argument references the kernel's compiled-in default function block.
385 .An -nosplit