|
|
add_audio_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_disk_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_mouse_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_net_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_timer_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_true_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
add_tty_randomness(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
altq(9) -- kernel interfaces for manipulating output queues on network interfaces
|
|
The ALTQ system is a framework to manage queuing disciplines on network interfaces. ALTQ introduces new macros to manipulate output queues. The output queue macros are used to abstract queue operation... |
|
arc4random(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
assert(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
audio(9) -- interface between low and high level audio drivers
|
|
The audio device driver is divided into a high level, hardware independent layer, and a low level, hardware dependent layer. The interface between these is the audio_hw_if structure. struct audio_hw_i... |
|
autoconf(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
bcmp(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
bdevvp(9) -- create a vnode for a device
|
|
The getdevvp() function creates a vnode for a device of type type with a device number of dev, and returns a pointer to it in vpp. Its arguments are: dev The device number of the desired device. vpp W... |
|
bintime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
binuptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
boot(9) -- halt or reboot the system
|
|
The boot() function handles final system shutdown, and either halts or reboots the system. The exact action to be taken is determined by the flags passed in howto and by whether or not the system has ... |
|
boottime(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... |
|
bounds_check_with_label(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
bus_dma(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_create(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_destroy(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_load(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_load_mbuf(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_load_raw(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_load_uio(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_sync(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamap_unload(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamem_alloc(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamem_free(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamem_map(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamem_mmap(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_dmamem_unmap(9) -- bus and machine independent DMA mapping interface
|
|
The bus_dma interface provides a bus and machine independent mechanism for managing DMA data transfers to and from devices. The basic abstraction is the bus_dmamap_t, a pointer to a structure which co... |
|
bus_space(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_alloc(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_barrier(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_copy_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_free(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_map(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_raw_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_read_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_multi_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_set_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_subregion(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_unmap(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_vaddr(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_multi_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_multi_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_multi_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_raw_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_1(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_2(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_4(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
bus_space_write_region_8(9) -- bus space manipulation functions
|
|
The bus_space functions exist to allow device drivers machine-independent access to bus memory and register areas. All of the functions and types described in this document can be used by including th... |
|
cdevvp(9) -- create a vnode for a device
|
|
The getdevvp() function creates a vnode for a device of type type with a device number of dev, and returns a pointer to it in vpp. Its arguments are: dev The device number of the desired device. vpp W... |
|
config_activate(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_attach(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_deactivate(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_defer(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_detach(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_found(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_found_sm(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_init(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_rootfound(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_rootsearch(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
config_search(9) -- autoconfiguration framework
|
|
Autoconfiguration is the process of matching hardware devices with an appropriate device driver. In its most basic form, autoconfiguration consists of the recursive process of finding and attaching al... |
|
copy(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyin(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyinstr(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyout(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copyoutstr(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
copystr(9) -- kernel copy functions
|
|
The copy functions are designed to copy contiguous data from one address to another. All but copystr() copy data from user-space to kernel-space or vice-versa. The copy routines provide the following ... |
|
cpu_switch(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
crypto(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_dispatch(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_done(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_freereq(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_freesession(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_getreq(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_kdispatch(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_kdone(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_kregister(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_newsession(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_register(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
crypto_unregister(9) -- API for cryptographic services in the kernel
|
|
crypto is a framework for drivers of cryptographic hardware to register with the kernel so ``consumers'' (other kernel subsystems, and eventually users through an appropriate device) are able to mak... |
|
ctxsw(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
db_printf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
disk(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
disk_attach(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_busy(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_detatch(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_find(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_init(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_resetstat(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
disk_unbusy(9) -- generic disk framework
|
|
The OpenBSD generic disk framework is designed to provide flexible, scalable, and consistent handling of disk state and metrics information. The fundamental component of this framework is the disk str... |
|
dohooks(9) -- run all hooks in a list
|
|
The dohooks() function invokes all hooks established using the hook_establish(9) function. Hooks are called in the order of the TAILQ that head points to, however hook_establish(9) can put the hooks e... |
|
dopowerhooks(9) -- run all power hooks
|
|
The dopowerhooks() function invokes all power hooks established using the powerhook_establish(9) function. At ``suspend'' and ``standby'' time, power hooks are called in reverse order, i.e., the p... |
|
doshutdownhooks(9) -- run all shutdown hooks
|
|
The doshutdownhooks() function invokes all shutdown hooks established using the shutdownhook_establish(9) function. Shutdown hooks are called in reverse order, i.e., the shutdown hook established last... |
|
dostartuphooks(9) -- run all startup hooks
|
|
The dostartuphooks() function invokes all startup hooks established using the startuphook_establish(9) function. Startup hooks are called in order, i.e., the startup hook established first will be cal... |
|
extattr(9) -- virtual file system named extended attributes
|
|
Named extended attributes allow additional meta-data to be associated with vnodes representing files and directories. The semantics of this additional data is that of a "name=value" pair, where a na... |
|
extent(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_alloc(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_alloc_region(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_alloc_subregion(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_create(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_destroy(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_free(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
extent_print(9) -- general purpose extent manager
|
|
The extent manager provides management of areas of memory or other enumerable spaces (such as I/O ports). An opaque structure called an extent map keeps track of allocated regions within the enumerabl... |
|
falloc(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
fdrelease(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
fd_getfile(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
ffs(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
file(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
fork1(9) -- create a new process
|
|
fork1() creates a new process out of p1, which should be the current process. This function is used primarily to implement the fork(2), rfork(2), vfork(2) system calls, as well as the kthread_create(9... |
|
free(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. free() releases memory at address addr that was previously allocated by mall... |
|
FREE(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. free() releases memory at address addr that was previously allocated by mall... |
|
FREF(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
FRELE(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
getbintime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getbinuptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getdevvp(9) -- create a vnode for a device
|
|
The getdevvp() function creates a vnode for a device of type type with a device number of dev, and returns a pointer to it in vpp. Its arguments are: dev The device number of the desired device. vpp W... |
|
getmicrotime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getmicrouptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getnanotime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getnanouptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
getnewvnode(9) -- get a new vnode
|
|
The getnewvnode() function initializes a new vnode, assigning it the vnode operations passed in vops. It will have its v_tag field set to tag and be placed in the mount queue for the mount point repre... |
|
getsn(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
getsock(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
getvnode(9) -- an overview of file descriptor handling
|
|
These functions provide the interface for the UNIX file descriptors. File descriptors can be used to access vnodes (see vnode(9)), sockets (see socket(2)), pipes (see pipe(2)), kqueues (see kqueue(2))... |
|
get_random_bytes(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
gsignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
hardclock(9) -- real-time system clock
|
|
hardclock() implements the real-time system clock, interrupting hz(9) times a second. The argument frame is an opaque, machine dependent structure that encapsulates the previous machine state. hardclo... |
|
hash(9) -- general kernel hashing functions
|
|
The hash32() functions are used to give a consistent and general interface to a decent hashing algorithm within the kernel. These functions can be used to hash ASCII NUL terminated strings, as well as... |
|
hashinit(9) -- kernel hashtable functions
|
|
The hashinit() function is used to allocate a hashtable of a desired size given by the num argument. The hashinit() function will round this number to the next power of two, and allocate and initializ... |
|
hook_disestablish(9) -- add or remove a hook from a specified list
|
|
The hook_establish() function adds fn to the list of hooks invoked by dohooks(9). If tail is non-zero, the hook is added to the tail of the list denoted by the TAILQ_HEAD pointer head, otherwise to th... |
|
hook_establish(9) -- add or remove a hook from a specified list
|
|
The hook_establish() function adds fn to the list of hooks invoked by dohooks(9). If tail is non-zero, the hook is added to the tail of the list denoted by the TAILQ_HEAD pointer head, otherwise to th... |
|
hz(9) -- system time model
|
|
The system is driven by hardclock(9) interrupts, which occur at hz frequency, and are used to keep track of real time. On systems where another independent clock is available, it is set at stathz freq... |
|
hzto(9) -- translate absolute time to timeout delay
|
|
The hzto() function computes the number of hz until the specified time occurs. This is mainly used to translate a timeval into a suitable argument for timeout(9). |
|
iic(9) -- Inter IC (I2C) bus
|
|
I2C is a two-wire bus developed by Philips used for connecting integrated circuits. It is commonly used for connecting devices such as EEPROMs, temperature sensors, fan controllers, real-time clocks, ... |
|
imax(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
imin(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
inittodr(9) -- initialize system time
|
|
The inittodr() function determines the time and sets the system clock. It tries to pick the correct time using a set of heuristics that examine the system's battery-backed clock and the time reported... |
|
intro(9) -- introduction to the kernel internals
|
|
The manual pages in section 9 contain information related to the internal kernel data structures, variables and functions. |
|
KASSERT(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
KDASSERT(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
kern(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
knote(9) -- raise kernel event
|
|
The knote() function provides a hook into the kqueue kernel event notification mechanism to allow sections of the kernel to raise a kernel event in the form of a `knote', which is a struct knote as d... |
|
KNOTE(9) -- raise kernel event
|
|
The knote() function provides a hook into the kqueue kernel event notification mechanism to allow sections of the kernel to raise a kernel event in the form of a `knote', which is a struct knote as d... |
|
kthread(9) -- kernel threads
|
|
Kernel threads are system light-weight processes: cloned from process 0 (the swapper), sharing its memory map and limits, but with a copy of its file descriptor table. They don't receive broadcast no... |
|
kthread_create(9) -- kernel threads
|
|
Kernel threads are system light-weight processes: cloned from process 0 (the swapper), sharing its memory map and limits, but with a copy of its file descriptor table. They don't receive broadcast no... |
|
kthread_create_deferred(9) -- kernel threads
|
|
Kernel threads are system light-weight processes: cloned from process 0 (the swapper), sharing its memory map and limits, but with a copy of its file descriptor table. They don't receive broadcast no... |
|
kthread_exit(9) -- kernel threads
|
|
Kernel threads are system light-weight processes: cloned from process 0 (the swapper), sharing its memory map and limits, but with a copy of its file descriptor table. They don't receive broadcast no... |
|
ktrace(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrcsw(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktremul(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrgenio(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrnamei(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
KTRPOINT(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrpsig(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrsyscall(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
ktrsysret(9) -- process tracing kernel interface
|
|
This interface is meant for kernel subsystems and machine dependent code to inform the user about the events occurring to the process should tracing of such be enabled using the ktrace(2) system call.... |
|
lmax(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
lmin(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
locc(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
lock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
lockinit(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
lockmgr(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
lockmgr_printinfo(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
lockstatus(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
log(9) -- log a message from the kernel through the /dev/klog device
|
|
The log() function allows the kernel to send formatted messages to user processes listening on /dev/klog. Usually syslogd(8) monitors /dev/klog for these messages and writes them to a log file. All me... |
|
lookup(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
malloc(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. free() releases memory at address addr that was previously allocated by mall... |
|
MALLOC(9) -- kernel memory allocator
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. free() releases memory at address addr that was previously allocated by mall... |
|
max(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
mbuf(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
mbuf_tags(9) -- a framework for generic packet attributes
|
|
These functions allow the manipulation of generic packet attributes. They are used by the kernel to keep track of operations done or scheduled to happen to packets. These attributes are attached to mb... |
|
MCHTYPE(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MCLGET(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
md5(9) -- message digest routines
|
|
The md5 module implements the RSA Data Security, Inc. MD5 Message-Digest Algorithm (MD5). It produces 128-bit MD5 Digest of data. MD5Init must be called just before MD5Transform() will be used to prod... |
|
MD5Init(9) -- message digest routines
|
|
The md5 module implements the RSA Data Security, Inc. MD5 Message-Digest Algorithm (MD5). It produces 128-bit MD5 Digest of data. MD5Init must be called just before MD5Transform() will be used to prod... |
|
MD5Transform(9) -- message digest routines
|
|
The md5 module implements the RSA Data Security, Inc. MD5 Message-Digest Algorithm (MD5). It produces 128-bit MD5 Digest of data. MD5Init must be called just before MD5Transform() will be used to prod... |
|
memchr(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
memcmp(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
MEXTADD(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MEXTALLOC(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MFREE(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MGET(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MGETHDR(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
MH_ALIGN(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
microtime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
microuptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
min(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
mi_switch(9) -- switch to another process context
|
|
The mi_switch() function implements the machine-independent prelude to a process context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of no... |
|
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... |
|
m_adj(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
M_ALIGN(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_apply(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_cat(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_copyback(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_copydata(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_copym(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_copym2(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_devget(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_free(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_freem(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_get(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_getclr(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_gethdr(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_getptr(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_inject(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
M_LEADINGSPACE(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
M_PREPEND(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_prepend(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_pulldown(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_pullup(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_pullup2(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
M_READONLY(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_reclaim(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_retry(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_retryhdr(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_split(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
M_TRAILINGSPACE(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
m_zero(9) -- Kernel memory management for networking protocols
|
|
The mbuf functions provide a way to manage the memory buffers used by the kernel's networking subsystem. Several functions and macros are used to allocate and deallocate mbufs, but also to get, injec... |
|
namei(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
nanotime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
nanouptime(9) -- system clock
|
|
This family of functions return the system clock in various different formats. The functions with the "uptime" suffix return the monotonically increasing time since boot. The functions without "up... |
|
NDINIT(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
panic(9) -- Bring down system on fatal error
|
|
The panic() function makes the OpenBSD system terminate. The message fmt is a printf(9) style format string. The message is printed to the console and the location pointed to by the global char pointe... |
|
pfind(9) -- find process / process group by number
|
|
The pfind() and pgfind() functions retrieve process and progress group structures from process and process group IDs. Both functions return NULL if the requested ID can't be found. |
|
pgfind(9) -- find process / process group by number
|
|
The pfind() and pgfind() functions retrieve process and progress group structures from process and process group IDs. Both functions return NULL if the requested ID can't be found. |
|
pgsignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
physio(9) -- initiate I/O on raw devices
|
|
physio() is a helper function typically called from character device read and write routines to start I/O on a user process buffer. It calls back on the provided strategy routine one or more times to ... |
|
pmap(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_clear_modify(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_clear_reference(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_collect(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_copy(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_copy_page(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_create(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_destroy(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_enter(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_growkernel(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_init(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_is_modified(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_is_referenced(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_kenter_pa(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_kremove(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_page_protect(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_protect(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_reference(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_remove(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_steal_memory(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_unwire(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_update(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_virtual_space(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pmap_zero_page(9) -- machine dependent interface to the MMU
|
|
The architecture-dependent pmap module describes how the physical mapping is done between the user-processes and kernel virtual addresses and the physical addresses of the main memory, providing machi... |
|
pool(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_destroy(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_destruct_object(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_get(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_init(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_invalidate(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_cache_put(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_destroy(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_get(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_init(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_prime(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_put(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_sethiwat(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
pool_setlowat(9) -- resource-pool manager
|
|
These utility routines provide management of pools of fixedsized areas of memory. Resource pools set aside an amount of memory for exclusive use by the resource pool owner. This can be used by applica... |
|
powerhook_disestablish(9) -- add or remove a power hook
|
|
The powerhook_establish() function adds fn to the list of hooks invoked by dopowerhooks(9) during any change in apm(4) power state (i.e., during a ``suspend'', ``standby'', or ``resume''). When ... |
|
powerhook_establish(9) -- add or remove a power hook
|
|
The powerhook_establish() function adds fn to the list of hooks invoked by dopowerhooks(9) during any change in apm(4) power state (i.e., during a ``suspend'', ``standby'', or ``resume''). When ... |
|
ppsratecheck(9) -- function to help implement rate-limited actions
|
|
The ppsratecheck() function provides an easy way to perform packet-persec, or event-per-sec, rate limitation. The motivation for implementing ppsratecheck() was to provide a mechanism that could be us... |
|
printf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
profhz(9) -- system time model
|
|
The system is driven by hardclock(9) interrupts, which occur at hz frequency, and are used to keep track of real time. On systems where another independent clock is available, it is set at stathz freq... |
|
psignal(9) -- post signal to a process
|
|
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the proc... |
|
radio(9) -- interface between low and high level radio drivers
|
|
The radio device driver is divided into a high level, hardware independent layer, and a low level hardware dependent layer. The interface between these is the radio_hw_if structure. struct radio_hw_if... |
|
random(9) -- device kernel interface
|
|
The add_mouse_randomness(), add_tty_randomness(), add_net_randomness(), add_disk_randomness() and add_audio_randomness() routines are used to supply data for the random data source device for further ... |
|
rasops(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
rasops_init(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
rasops_reconfig(9) -- raster display operations
|
|
The rasops subsystem is a set of raster operations for wscons(9). The primary data type for using the raster operations is the rasops_info structure in dev/rasops/rasops.h: struct rasops_info { /* * T... |
|
ratecheck(9) -- function to help implement rate-limited actions
|
|
The ratecheck() function provides a simple time interval check which can be used when implementing time-based rate-limited actions. If the difference between the current monotonically-increasing syste... |
|
readdisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
relookup(9) -- pathname lookup
|
|
The namei interface is used to convert pathnames to file system vnodes. The name of the interface is actually a contraction of the words name and inode for name-to-inode conversion, in the days before... |
|
resettodr(9) -- set battery-backed clock from system time
|
|
The resettodr() function sets the system's battery backed clock based on the contents of the system time variable. |
|
runtime(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... |
|
scanc(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
setdisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
|
shutdownhook_disestablish(9) -- add or remove a shutdown hook
|
|
The shutdownhook_establish() function adds fn to the list of hooks invoked by doshutdownhooks(9) at shutdown. When invoked, the hook function fn will be passed arg as its only argument. The shutdownho... |
|
shutdownhook_establish(9) -- add or remove a shutdown hook
|
|
The shutdownhook_establish() function adds fn to the list of hooks invoked by doshutdownhooks(9) at shutdown. When invoked, the hook function fn will be passed arg as its only argument. The shutdownho... |
|
simple_lock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
simple_lock_init(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
simple_lock_try(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
simple_unlock(9) -- kernel lock functions
|
|
The lock functions provide synchronisation in the kernel by preventing multiple processes from simultaneously executing critical sections of code accessing shared data. A number of different locks are... |
|
skpc(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
sleep(9) -- process context sleep and wakeup
|
|
These functions implement voluntary context switching. tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the following reasons:... |
|
snprintf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
spl(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
spl0(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splassert(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splbio(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splhigh(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splimp(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
spllowersoftclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splnet(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splsched(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splserial(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splsoftclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splsoftnet(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splsoftserial(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splsofttty(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splstatclock(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
spltty(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splvm(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
splx(9) -- modify system interrupt priority level
|
|
These functions raise and lower the system priority level. They are used by kernel code to block interrupts with priority less than or equal to the named level (i.e., spltty() blocks interrupts of pri... |
|
srandom(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
startuphook_disestablish(9) -- add or remove a startup hook
|
|
The startuphook_establish() function adds fn to the list of hooks invoked by dostartuphooks(9) at startup. When invoked, the hook function fn will be passed arg as its only argument. The startuphook_d... |
|
startuphook_establish(9) -- add or remove a startup hook
|
|
The startuphook_establish() function adds fn to the list of hooks invoked by dostartuphooks(9) at startup. When invoked, the hook function fn will be passed arg as its only argument. The startuphook_d... |
|
stathz(9) -- system time model
|
|
The system is driven by hardclock(9) interrupts, which occur at hz frequency, and are used to keep track of real time. On systems where another independent clock is available, it is set at stathz freq... |
|
strcmp(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strlcat(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strlcpy(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strlen(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strncasecmp(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strncmp(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
strncpy(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
style(9) -- Kernel source file style guide (KNF)
|
|
This file specifies the preferred style for kernel source files in the OpenBSD source tree. It is also a guide for preferred user land code style. These guidelines should be followed for all new code.... |
|
syscall(9) -- system calls overview
|
|
System calls in the kernel are implemented through a set of switch tables for each emulation type. Each table is generated from the ``master'' file by sys/kern/makesyscalls.sh through the appropriat... |
|
systrace(9) -- enforce policies for system calls
|
|
These functions are used to enforce policy on the system calls as described in systrace(1). systrace_redirect() should be used to perform a system call number code with arguments args for the process ... |
|
systrace_exit(9) -- enforce policies for system calls
|
|
These functions are used to enforce policy on the system calls as described in systrace(1). systrace_redirect() should be used to perform a system call number code with arguments args for the process ... |
|
systrace_fork(9) -- enforce policies for system calls
|
|
These functions are used to enforce policy on the system calls as described in systrace(1). systrace_redirect() should be used to perform a system call number code with arguments args for the process ... |
|
systrace_redirect(9) -- enforce policies for system calls
|
|
These functions are used to enforce policy on the system calls as described in systrace(1). systrace_redirect() should be used to perform a system call number code with arguments args for the process ... |
|
tick(9) -- system time model
|
|
The system is driven by hardclock(9) interrupts, which occur at hz frequency, and are used to keep track of real time. On systems where another independent clock is available, it is set at stathz freq... |
|
tickadj(9) -- system time model
|
|
The system is driven by hardclock(9) interrupts, which occur at hz frequency, and are used to keep track of real time. On systems where another independent clock is available, it is set at stathz freq... |
|
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... |
|
timeout(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_add(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_del(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_initialized(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_pending(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_set(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
timeout_triggered(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
tsleep(9) -- process context sleep and wakeup
|
|
These functions implement voluntary context switching. tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the following reasons:... |
|
ttyprintf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
tvtohz(9) -- translate time period to timeout delay
|
|
The tvtohz() function computes the number of hz in the specified amount of time. This is mainly used to translate a timeval into a suitable argument for timeout(9). |
|
uao_create(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uao_detach(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uao_reference(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uio(9) -- move data described by a struct uio
|
|
The uiomove function copies up to n bytes between the kernel-space address pointed to by buf and the addresses described by uio, which may be in user-space or kernel-space. The uio argument is a point... |
|
uiomove(9) -- move data described by a struct uio
|
|
The uiomove function copies up to n bytes between the kernel-space address pointed to by buf and the addresses described by uio, which may be in user-space or kernel-space. The uio argument is a point... |
|
ulmax(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
ulmin(9) -- kernel library routines
|
|
The kern library implements a set of useful functions and macros inside the kernel. |
|
untimeout(9) -- execute a function after a specified period of time
|
|
The timeout API provides a mechanism to execute a function at a given time. The granularity of the time is limited by the granularity of the hardclock(9) timer which executes hz(9) times a second. The... |
|
uprintf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
uvm(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_alloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_exec(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_fork(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_free(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_share(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvmspace_unshare(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_chgkprot(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_coredump(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_deallocate(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_fault(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_fork(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_grow(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_init(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_init_limits(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_io(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_kernacc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_alloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_alloc1(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_free(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_free_wakeup(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_kmemalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_suballoc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_valloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_valloc_wait(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_km_zalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
UVM_MAPFLAG(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_checkprot(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_pageable(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_pageable_all(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_map_protect(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_meter(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagealloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagefree(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pageout(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pagerealloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_page_physload(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pglistalloc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_pglistfree(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_scheduler(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_setpagesize(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_swapin(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_swap_init(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_sysctl(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_useracc(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vnp_setsize(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vnp_sync(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vnp_terminate(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vnp_uncache(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vslock(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvm_vsunlock(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
uvn_attach(9) -- virtual memory system external interface
|
|
The UVM virtual memory system manages access to the computer's memory resources. User processes and the kernel access these resources through UVM's external interface. UVM's external interface incl... |
|
vaccess(9) -- check access permissions based on vnode parameters
|
|
The vaccess() function checks if the credentials described in cred are sufficient to perform the operation described by acc_mode, based on the file_mode, uid, and gid arguments. These arguments would ... |
|
vclean(9) -- disassociate the underlying file system from a vnode
|
|
The vclean() function clears any VM and buffer data associated with the vnode vp and reclaims it from the underlying file system. Its arguments are: vp The vnode to be cleaned. flags The flags indicat... |
|
vcount(9) -- get total number of references to a device
|
|
vcount() is used to get the number of references to a particular device. It allows for the fact that multiple vnodes may reference the same device. |
|
vdevgone(9) -- revoke all specified minor numbered vnodes for a device
|
|
The vdevgone() function will revoke all the vnodes corresponding to the specified minor number range for the device with a major number of maj and of type type. Its arguments are: maj The major number... |
|
vfinddev(9) -- lookup a vnode by device number
|
|
The vfinddev() function returns a pointer to the vnode of the device represented by the device number dev and of type type in vpp. |
|
vflush(9) -- flush vnodes for a mount point
|
|
The vflush() function removes any vnodes in the vnode table that belong to the given mount structure. Its arguments are: mp The mount point whose vnodes should be removed. skipvp If this is given, the... |
|
vfs(9) -- kernel interface to file systems
|
|
The virtual file system, VFS, is the kernel interface to file systems. The interface specifies the calls for the kernel to access file systems. It also specifies the core functionality that a file sys... |
|
vget(9) -- get a vnode from the free list
|
|
Get a vnode from the free list and increment its reference count. Its arguments are: vp The vnode to remove from the free list. flags If non-zero, the vnode will also be locked. p The process responsi... |
|
vgone(9) -- prepare a vnode for reuse
|
|
vgone() and vgonel() prepare a vnode for reuse by another file system. The preparation includes the cleaning of all file system specific data and the removal from its mount point vnode list. The diffe... |
|
vgonel(9) -- prepare a vnode for reuse
|
|
vgone() and vgonel() prepare a vnode for reuse by another file system. The preparation includes the cleaning of all file system specific data and the removal from its mount point vnode list. The diffe... |
|
vhold(9) -- acquire a hold on a vnode
|
|
The vhold() function increments the v_holdcnt of the given vnode. If the vnode has already been added to the free list and its v_holdcnt and v_usecount are both zero, it will be removed from the free ... |
|
vinvalbuf(9) -- flush and invalidate all buffers associated with a vnode
|
|
The vinvalbuf() function invalidates all of the buffers associated with the given vnode. This includes buffers on the clean list and the dirty list. If the V_SAVE flag is specified then the buffers on... |
|
vnode(9) -- an overview of vnodes
|
|
A vnode is an object in kernel memory that speaks the UNIX file interface (open, read, write, close, readdir, etc.). Vnodes can represent files, directories, FIFOs, domain sockets, block devices, char... |
|
vn_lock(9) -- acquire the vnode lock
|
|
The vn_lock() function is used to acquire the vnode lock. Certain file system operations require that the vnode lock be held when they are called. See sys/kern/vnode_if.src for more details. The vn_lo... |
|
VOP_CREATE(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_FSYNC(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_GETEXTATTR(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_ISLOCKED(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_LINK(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_LOCK(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_LOOKUP(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_MKDIR(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_PRINT(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_READLINK(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_REALLOCBLKS(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_RECLAIM(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_REMOVE(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_REVOKE(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_RMDIR(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_SETEXTATTR(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_STRATEGY(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_SYMLINK(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_UNLOCK(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
VOP_WHITEOUT(9) -- vnode operations
|
|
The VOP functions implement a generic way to perform operations on vnodes. The VOP function called passes the arguments to the correct file system specific function. Not all file systems implement all... |
|
vprintf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
vput(9) -- decrement the reference count for a vnode and unlock it
|
|
Decrement the v_usecount field of the vnode vp and unlock the vnode. This operation is functionally equivalent to calling VOP_UNLOCK() followed by vrele(9). |
|
vrecycle(9) -- recycle a vnode if its reference count is zero
|
|
The vrecycle() function places the vnode vp on the free list using vgonel(9) if its v_usecount field is zero. If v_usecount is non-zero, it simply returns. If v_usecount is zero and an interlock inter... |
|
vref(9) -- increment the use count for a vnode
|
|
Increment the v_usecount field of the vnode specified by vp. Each vnode maintains a reference count of how many parts of the system are using the vnode. This allows the system to detect when a vnode i... |
|
vrele(9) -- decrement the use count for a vnode
|
|
Decrement the v_usecount field of the vnode specified by vp. Any code in the system which uses a vnode should call vrele() when it is finished with the vnode. If the v_usecount field of the vnode reac... |
|
vsnprintf(9) -- kernel formatted output conversion
|
|
The printf(), snprintf(), vprintf(), vsnprintf(), uprintf(), ttyprintf(), and db_printf() functions allow the kernel to send formatted messages to various output devices. The functions printf() and vp... |
|
vwaitforio(9) -- wait for all outstanding asynchronous writes
|
|
The vwaitforio() call sleeps until all asynchronous writes associated with the vnode vp finish. This is used by functions that need to make sure that the writes they initiated have completed. The vwai... |
|
wakeup(9) -- process context sleep and wakeup
|
|
These functions implement voluntary context switching. tsleep() and sleep() are used throughout the kernel whenever processing in the current context can not continue for any of the following reasons:... |
|
writedisklabel(9) -- disk label management routines
|
|
This collection of routines provides a disklabel management interface to kernel device drivers. These routines are classified as machine- or architecture-dependent because of restrictions imposed by t... |
