|accf_name||Name of the filter; this is how it will be accessed from userland.|
|The callback that the kernel will do once the connection is established. It is the same as a socket upcall and will be called when the connection is established and whenever new data arrives on the socket, unless the callback modifies the sockets flags.|
|accf_create||Called whenever a setsockopt(2) installs the filter onto a listening socket.|
|accf_destroy||Called whenever the user removes the accept filter on the socket.|
The accept_filt_del function passed the same string used in accept_filter.accf_name during registration with accept_filt_add, the kernel will then disallow and further userland use of the filter.
The accept_filt_get function is used internally to locate which accept filter to use via the setsockopt(2) system call.
function provides a simple way to avoid duplication of code
for accept filters which do not use the argument field to load
and unload themselves.
This function can be used in the
.Vt moduledata_t struct for the DECLARE_MODULE(9) macro.
setsockopt(2), accf_data(9), accf_dns(9), accf_http(9), malloc(9)
The accept filter mechanism was introduced in
.Fx 4.0 .
This manual page was written by
.An Alfred Perlstein ,
.An Sheldon Hearn and
.An Jeroen Ruigrok van der Werven.
The accept filter concept was pioneered by
.An David Filo at Yahoo! and refined to be a loadable module system by
.An Alfred Perlstein .