Lines Matching +full:- +full:function

57 Additionally, users can specify a particular stack to use on a per-connection
64 This man page treats "TCP stacks" as synonymous with "function blocks".
67 Therefore, an alternate "function block" defines an alternate "TCP stack".
74 functions request that the system add a specified function block
76 Modules may register the same function block multiple times with different
78 However, names must be globally unique among all registered function blocks.
79 Also, modules may not ever modify the contents of the function block (including
81 de-registers the function block.
85 function requests that the system register the function block with the name
86 defined in the function block's
90 automatically registers the function block using the name defined in the
91 function block's
95 the system register the function block using the name defined in the
96 function block's
102 function requests that the system register the function block with the name
109 function requests that the system register the function block with all the
117 This function will either succeed in registering all of the names in the array,
127 function requests that the system remove a specified function block from the
129 If this call succeeds, it will completely deregister the function block,
130 regardless of the number of names used to register the function block.
131 If the call fails because sockets are still using the specified function block,
132 the system will mark the function block as being in the process of being
134 This will prevent additional sockets from using the specified function block.
135 However, it will not impact sockets that are already using the function block.
141 function prior to allowing the module to be unloaded.
148 .Sx Function Block Structure ) .
156 .Ss Function Block Structure
161 .Bd -literal -offset indent
181 	/* Optional function */
183 	/* Mandatory function */
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
216 TCP stack (or, when the socket is closed), it should set a non-NULL pointer
223 argument is non-NULL, the function to which it points is called when the
226 The function is called with arguments of the TCP control block and an integer
232 non-NULL pointer in the
258 timer fires by setting a non-NULL function pointer in the
261 This function is called very early in the process of handling a retransmit
268 Therefore, the function pointer
270 field must be non-NULL.
271 If a user attempts to select that TCP stack, the kernel will call the function
275 The function should return 0 if the user is allowed to switch the socket to use
276 the TCP stack. In this case, the kernel will call the function pointed to by
278 if this function pointer is non-NULL and finally perform the stack switch.
279 If the user is not allowed to switch the socket, the function should undo any
291 TCP control block, the TCP stack can initialize its own per-connection storage.
297 per-connection storage.
305 function to initialize this field.
308 function to deallocate storage when the socket is closed.
321 functions return zero on success and non-zero on failure.
338 .Bl -tag -width Er
344 The function could not allocate memory for its internal data.
348 is already registered or a function block is already registered with the same
354 .Bl -tag -width Er
362 function will fail if:
363 .Bl -tag -width Er
367 argument references the kernel's compiled-in default function block.
369 The function block is still in use by one or more sockets, or is defined as
370 the current default function block.
374 argument references a function block that is not currently registered.
385 .An -nosplit