|
|
|
sx_init(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_slock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
|
sx_sunlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
SX_SYSINIT(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_slock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_upgrade(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_xlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_xlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_xunlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
SYSCALL_MODULE(9) -- syscall kernel module declaration macro
|
|
The SYSCALL_MODULE() macro declares a new syscall. SYSCALL_MODULE() expands into a kernel module declaration named as name. offset is a pointer to an int which saves the offset in struct sysent where ... |
|
SYSCTL_ADD_INT(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_LONG(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_NODE(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
sysctl_add_oid(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_OID(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
