|
|
|
minor(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
mi_switch(9) -- switch to another thread context
|
|
The mi_switch() function implements the machine independent prelude to a thread context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of non... |
|
|
module(9) -- structure describing a kernel module
|
|
Each module in the kernel is described by a module_t structure. The structure contains the name of the device, a unique ID number, a pointer to an event handler function and to an argument, which is g... |
|
MODULE_DEPEND(9) -- set kernel module dependencies
|
|
The MODULE_DEPEND() macro sets a dependency on another kernel module with name moddepend, which has been registered its version with MODULE_VERSION(). Three versions must be specified on which the mod... |
|
MODULE_VERSION(9) -- set kernel module version
|
|
The MODULE_VERSION() macro sets the version of the module called name. Other kernel modules can then depend on this module (see MODULE_DEPEND(9)). |
|
mono_time(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
msleep(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
mtx_assert(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_destroy(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_init(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_initialized(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_spin(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_spin_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
