|
|
accf_http(9) -- buffer incoming connections until a certain complete HTTP requests arrive
|
|
This is a filter to be placed on a socket that will be using accept() to receive incoming HTTP connections. It prevents the application from receiving the connected descriptor via accept() until eithe... |
|
acl(9) -- virtual file system access control lists
|
|
Access control lists, or ACLs, allow fine-grained specification of rights for vnodes representing files and directories. However, as there are a plethora of file systems with differing ACL semantics, ... |
|
alq(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
ALQ(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_close(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_flush(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_get(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_open(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_post(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
alq_write(9) -- Asynchronous Logging Queues
|
|
The alq facility provides an asynchronous fixed length recording mechanism, known as Asynchronous Logging Queues. It can record to any vnode(9), thus providing the ability to journal logs to character... |
|
arc4rand(9) -- supply pseudo-random numbers
|
|
The random() function will by default produce a sequence of numbers that can be duplicated by calling srandom() with `1' as the seed. The srandom() function may be called with any arbitrary seed valu... |
|
arc4random(9) -- supply pseudo-random numbers
|
|
The random() function will by default produce a sequence of numbers that can be duplicated by calling srandom() with `1' as the seed. The srandom() function may be called with any arbitrary seed valu... |
|
atomic(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_add(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_clear(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_cmpset(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_load(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_readandclear(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_set(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_store(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
atomic_subtract(9) -- atomic operations
|
|
Each of the atomic operations is guaranteed to be atomic in the presence of interrupts. They can be used to implement reference counts or as building blocks for more advanced synchronization primitive... |
|
be16dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be16enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be16toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be32dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be32enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be32toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be64dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be64enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
be64toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
bios(9) -- interact with PC BIOS
|
|
These functions provide a general-purpose interface for dealing with the BIOS functions and data encountered on x86 PC-architecture systems. bios_sigsearch() Searches the BIOS address space for a serv... |
|
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... |
|
bp(9) -- kernel buffer I/O scheme used in FreeBSD VM system
|
|
The kernel implements a KVM abstraction of the buffer cache which allows it to map potentially disparate vm_page's into contiguous KVM for use by (mainly file system) devices and device I/O. This abs... |
|
bswap16(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
bswap32(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
bswap64(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
buf(9) -- kernel buffer I/O scheme used in FreeBSD VM system
|
|
The kernel implements a KVM abstraction of the buffer cache which allows it to map potentially disparate vm_page's into contiguous KVM for use by (mainly file system) devices and device I/O. This abs... |
|
BUF_LOCK(9) -- locks a buffer
|
|
The BUF_LOCK() function locks the given buffer. If the lock is already held this call will block until it can acquire the lock unless LK_NOWAIT is set. Its arguments are: bp The buffer to lock. lockty... |
|
BUF_LOCKFREE(9) -- destroys a buffer's lock
|
|
The BUF_LOCKFREE() macro destroys the buffer lock. The lock must not be held when this macro is called or a panic will result. Its argument is: bp The buffer whose lock is to be destroyed. |
|
BUF_LOCKINIT(9) -- unlocks a locked buffer
|
|
The BUF_LOCKINIT() macro initializes a buffer lock. Its argument is: bp The buffer whose lock it to be initialized. |
|
BUF_REFCNT(9) -- returns the reference count on a buffer's lock
|
|
The BUF_REFCNT() function returns the reference count on a buffer's lock. Its argument is: bp The buffer whose lock reference count is to be returned. |
|
BUF_TIMELOCK(9) -- locks a buffer
|
|
The BUF_TIMELOCK() function locks the given buffer, and limits the amount of time it will sleep to timo and OR's catch into the sleep's priority. wmesg is the wmesg used in the sleep. Its arguments ... |
|
BUF_UNLOCK(9) -- unlocks a locked buffer
|
|
The BUF_UNLOCK() function unlocks a buffer that was previously locked with BUF_LOCK() or BUF_TIMELOCK(). Its argument is: bp The buffer to unlock. The buffer must already be locked. |
|
busdma(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_activate_resource(9) -- activate or deactivate a resource
|
|
These functions activate or deactivate a previously allocated resource. In general, resources must be activated before they can be accessed by the driver so that the bus driver can map the resource in... |
|
bus_alloc_resource(9) -- alloc resources on a bus
|
|
This is an easy interface to the resource-management functions. It hides the indirection through the parent's method table. This function generally should be called in attach, but (except in some rar... |
|
bus_child_present(9) -- ask the bus driver to see if this device is still really present
|
|
The bus_child_present() function requests that the parent device driver of dev check to see if the hardware represented by dev is still physically accessible at this time. While the notion of accessib... |
|
BUS_CONFIG_INTR(9) -- Configure interrupt polarity and trigger mode
|
|
The BUS_CONFIG_INTR method allows bus or device drivers to provide interrupt polarity and trigger mode to parent busses. This typically bubbles all the way up to the root bus (e.g. nexus) where the ne... |
|
bus_deactivate_resource(9) -- activate or deactivate a resource
|
|
These functions activate or deactivate a previously allocated resource. In general, resources must be activated before they can be accessed by the driver so that the bus driver can map the resource in... |
|
bus_dma(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_create(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_destroy(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_load(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_load_mbuf(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_load_uio(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_sync(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamap_unload(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamem_alloc(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dmamem_free(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dma_tag_create(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_dma_tag_destroy(9) -- Bus and Machine Independent DMA Mapping Interface
|
|
Direct Memory Access (DMA) is a method of transferring data without involving the CPU, thus providing higher performance. A DMA transaction can be achieved between device to memory, device to device, ... |
|
bus_generic_attach(9) -- generic implementation of DEVICE_ATTACH for busses
|
|
This function provides an implementation of the DEVICE_ATTACH(9) method which can be used by most bus code. It simply calls device_probe_and_attach(9) for each child device attached to the bus. |
|
bus_generic_detach(9) -- generic implementation of DEVICE_DETACH for busses
|
|
This function provides an implementation of the DEVICE_DETACH(9) method which can be used by most bus code. It simply calls the DEVICE_DETACH(9) method of each child device attached to the bus. |
|
bus_generic_print_child(9) -- generic implementation of DEVICE_PRINT_CHILD for busses
|
|
This implementation prints out the default device announcement message. Given device 'foo0' on bus 'bar0' where foo0 has the name "FooCard 1234" the following would be printed: foo0: |
|
bus_generic_read_ivar(9) -- generic implementation of BUS_READ_IVAR and BUS_WRITE_IVAR for busses
|
|
These functions simply return ENOENT. |
|
bus_generic_shutdown(9) -- generic implementation of DEVICE_SHUTDOWN for busses
|
|
This function provides an implementation of the DEVICE_SHUTDOWN(9) method which can be used by most bus code. It simply calls the DEVICE_SHUTDOWN(9) method of each child device attached to the bus. |
|
bus_generic_write_ivar(9) -- generic implementation of BUS_READ_IVAR and BUS_WRITE_IVAR for busses
|
|
These functions simply return ENOENT. |
|
BUS_PRINT_CHILD(9) -- print information about a device
|
|
This is called from system code which prints out a description of a device. It should describe the attachment that the child has with the parent. For instance the TurboLaser bus prints which node the ... |
|
BUS_READ_IVAR(9) -- manipulate bus-specific device instance variables
|
|
These two methods manage a bus specific set of instance variables of a child device. The intention is that each different type of bus defines a set of appropriate instance variables (such as ports and... |
|
bus_release_resource(9) -- release resources on a bus
|
|
Free a resource allocated by bus_alloc_resource(9). The resource must not be in use on release, i.e. call an appropriate function before (e.g. bus_teardown_intr(9) for IRQs). dev is the device that ow... |
|
BUS_SETUP_INTR(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
|
bus_setup_intr(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
|
bus_set_resource(9) -- associate a definite resource with a given resource ID
|
|
The bus_set_resource() function sets the start address of the resource type, rid pair to be count long. Typically, client drivers do not use this interface. Bus drivers, however, often use it to set u... |
|
BUS_TEARDOWN_INTR(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
|
bus_teardown_intr(9) -- create, attach and teardown an interrupt handler
|
|
The method BUS_SETUP_INTR will create and attach an interrupt handler to an interrupt previously allocated by the resource manager's BUS_ALLOC_RESOURCE(9) method. The flags are found in , ... |
|
BUS_WRITE_IVAR(9) -- manipulate bus-specific device instance variables
|
|
These two methods manage a bus specific set of instance variables of a child device. The intention is that each different type of bus defines a set of appropriate instance variables (such as ports and... |
|
byteorder(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
callout_handle_init(9) -- execute a function after a specified length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
callout_init(9) -- execute a function after a specified length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
callout_reset(9) -- execute a function after a specified length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
callout_stop(9) -- execute a function after a specified length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
cd(9) -- CDROM driver for the CAM SCSI subsystem
|
|
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type commands. Some drives don't behave as the driver expects. See ... |
|
cdevsw_add(9) -- adds a cdevsw entry
|
|
The cdevsw_add() function adds newentry to the cdevsw table if its major number is greater than or equal to zero, and is less than NUMCDEVSW. Its argument is: newentry The device to add to the table. |
|
cdevsw_remove(9) -- removes a cdevsw entry
|
|
The cdevsw_remove() function removes oldentry from the cdevsw table if its major number is greater than or equal to zero, and is less than NUMCDEVSW. Its argument is: oldentry The device to remove fro... |
|
chooseproc(9) -- manage the queue of runnable processes
|
|
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. E... |
|
condvar(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
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 ... |
|
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 ... |
|
count_dev(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. count_dev() does the same thing as vcount(), but tak... |
|
cpu_critical_enter(9) -- enter and exit a critical region
|
|
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a c... |
|
cpu_critical_exit(9) -- enter and exit a critical region
|
|
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a c... |
|
cpu_switch(9) -- switch to another thread context
|
|
The mi_switch() function implements the machine independent prelude to a thread context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of non... |
|
cpu_throw(9) -- switch to another thread context
|
|
The mi_switch() function implements the machine independent prelude to a thread context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of non... |
|
crcopy(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
crdup(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
crfree(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
crget(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
crhold(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
critical_enter(9) -- enter and exit a critical region
|
|
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a c... |
|
critical_exit(9) -- enter and exit a critical region
|
|
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a c... |
|
crshared(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
cru2x(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
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 users through the /dev/crypto device) are able to make use of i... |
|
CTASSERT(9) -- compile time assertion macro
|
|
The CTASSERT() macro evaluates expression at compile time and causes a compiler error if it is false. The CTASSERT() macro is useful for asserting the size or alignment of important data structures an... |
|
CTR0(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
CTR1(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
CTR2(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
CTR3(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
CTR4(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
CTR5(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
curpriority_cmp(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
CURSIG(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
cv_broadcast(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_destroy(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_init(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_signal(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_timedwait(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_timedwait_sig(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_wait(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_waitq_empty(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_waitq_remove(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_wait_sig(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
cv_wmesg(9) -- kernel condition variable
|
|
Condition variables are used in conjunction with mutexes to wait for conditions to occur. Condition variables are created with cv_init(), where cvp is a pointer to space for a struct cv, and desc is a... |
|
DECLARE_MODULE(9) -- kernel module declaration macro
|
|
The DECLARE_MODULE() macro declares a generic kernel module. It is used to register the module with the system, using the SYSINIT() macro. DECLARE_MODULE() is usually used within other macros, such as... |
|
DEFINE_CLASS(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
DELAY(9) -- busy loop for an interval
|
|
Delay for delay microseconds (1/1000000th of a second). |
|
destroy_dev(9) -- manage dev_t's and DEVFS registration for devices
|
|
The make_dev() function creates a dev_t structure for a new device. If DEVFS is available, it is also notified of the presence of the new device. The device will be owned by uid, with the group owners... |
|
devclass(9) -- object representing a class of devices
|
|
The devclass object has two main functions in the system. The first is to manage the allocation of unit numbers for device instances and the second is to hold the list of device drivers for a particul... |
|
devclass_add_driver(9) -- manipulate the drivers in a devclass
|
|
These functions can be used to add new drivers into the system, remove old ones and search for existing ones. Normally drivers are added automatically during system initialisation. |
|
devclass_delete_driver(9) -- manipulate the drivers in a devclass
|
|
These functions can be used to add new drivers into the system, remove old ones and search for existing ones. Normally drivers are added automatically during system initialisation. |
|
devclass_find(9) -- search for a devclass
|
|
Search for the devclass with the specified name. |
|
devclass_find_driver(9) -- manipulate the drivers in a devclass
|
|
These functions can be used to add new drivers into the system, remove old ones and search for existing ones. Normally drivers are added automatically during system initialisation. |
|
devclass_get_device(9) -- translate unit number to device
|
|
This function retrieves the device instance with the given unit number and returns it. |
|
devclass_get_devices(9) -- get a list of devices in a devclass
|
|
Retrieve a list of all device instances currently in the devclass and return the list in *devlistp and the count in *devcountp. The memory allocated for the list should be freed using free(*devlistp, ... |
|
devclass_get_maxunit(9) -- find the maximum unit number in the class
|
|
Returns the maximum unit number allocated to device instances in the specified devclass. |
|
devclass_get_name(9) -- access the name of a devclass
|
|
Return the name of a devclass. |
|
devclass_get_softc(9) -- translate unit number to driver private structure
|
|
This function retrieves the driver private instance variables for the device with the given unit number and returns it. |
|
device(9) -- an abstract representation of a device
|
|
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into, disk drives attached to the expansion card etc. The system d... |
|
devicestat(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
device_add_child(9) -- add a new device as a child of an existing device
|
|
Create a new child device of dev. The name and unit arguments specify the name and unit number of the device. If the name is unknown then the caller should pass NULL. If the unit is unknown then the c... |
|
device_add_child_ordered(9) -- add a new device as a child of an existing device
|
|
Create a new child device of dev. The name and unit arguments specify the name and unit number of the device. If the name is unknown then the caller should pass NULL. If the unit is unknown then the c... |
|
DEVICE_ATTACH(9) -- attach a device
|
|
Attach a device to the system. The probe method will have been called and will have indicated that the device exists. This routine should initialise the hardware and allocate other system resources (s... |
|
device_busy(9) -- manipulate device state
|
|
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY (described in device(9)). To test see if a device was successfully... |
|
device_delete_child(9) -- delete a child from a device
|
|
The specified device is removed from dev and deleted. If the device is currently attached, it is first detached (see DEVICE_ATTACH(9) and DEVICE_DETACH(9)). |
|
DEVICE_DETACH(9) -- detach a device
|
|
Detach a device. This can be called if the user is replacing the driver software or if a device is about to be physically removed from the system (e.g. for pccard devices). The method should deallocat... |
|
device_disable(9) -- manipulate device enabled flag
|
|
Each device has an enabled flag associated with it. A device is enabled by default when it is created but may be disabled (for instance to prevent a destructive or time consuming probe attempt). To di... |
|
device_enable(9) -- manipulate device enabled flag
|
|
Each device has an enabled flag associated with it. A device is enabled by default when it is created but may be disabled (for instance to prevent a destructive or time consuming probe attempt). To di... |
|
device_find_child(9) -- search for a child of a device
|
|
This function looks for a specific child of dev. with the given name and unit. |
|
device_get_children(9) -- get a list of devices connected to a device
|
|
Retrieve a list of all device instances currently connected to dev and return the list in *devlistp and the count in *devcountp. The memory allocated for the list should be freed using free(*devlistp,... |
|
device_get_desc(9) -- access the description of a device
|
|
Manipulate the verbose description of a device. This description (if present) is printed as part of the message when it is attached during autoconfiguration. The variation device_set_desc_copy() is us... |
|
device_get_devclass(9) -- access the devclass of a device
|
|
The current devclass associated with the device is returned. If the device has no devclass, NULL is returned. |
|
device_get_driver(9) -- access the current driver of a device
|
|
The current driver associated with the device is returned. If the device has no driver, NULL is returned. |
|
device_get_flags(9) -- manipulate driver flags
|
|
Each device supports a set of driver-dependent flags which are often used to control device behaviour. These flags are read by calling device_get_flags() and written by calling device_set_flags(). |
|
device_get_ivars(9) -- access bus private variables
|
|
The device_get_ivars() function returns the bus-specific instance variables of a device. The device_set_ivars() function sets the bus-specific instance variables of a device. Typically, only bus drive... |
|
device_get_name(9) -- access the name of a device's device class or instance
|
|
The device_get_name() function returns the name of the device's device class. The device_get_nameunit() function returns the name of the device's instance. |
|
device_get_nameunit(9) -- access the name of a device's device class or instance
|
|
The device_get_name() function returns the name of the device's device class. The device_get_nameunit() function returns the name of the device's instance. |
|
device_get_parent(9) -- return the device's parent
|
|
The device_get_parent() function returns the name of the device's parent device. |
|
device_get_softc(9) -- access driver private instance variables
|
|
Return the driver-specific state of dev. The softc is automatically allocated the first time it is requested. The size of the allocation is determined by the device's driver_t information used to def... |
|
device_get_state(9) -- manipulate device state
|
|
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY (described in device(9)). To test see if a device was successfully... |
|
device_get_unit(9) -- access the unit number of a device
|
|
Return the unit number of the device. |
|
DEVICE_IDENTIFY(9) -- identify a device, register it
|
|
The identify function for a device is only needed for devices on busses that cannot identify their children independently, e.g. the ISA bus. It is used to recognize the device (usually done by accessi... |
|
device_ids(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
device_is_alive(9) -- manipulate device state
|
|
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY (described in device(9)). To test see if a device was successfully... |
|
device_is_attached(9) -- manipulate device state
|
|
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY (described in device(9)). To test see if a device was successfully... |
|
device_is_enabled(9) -- manipulate device enabled flag
|
|
Each device has an enabled flag associated with it. A device is enabled by default when it is created but may be disabled (for instance to prevent a destructive or time consuming probe attempt). To di... |
|
device_is_quiet(9) -- manipulate device quiet flag
|
|
Each device has a quiet flag associated with it. A device is verbose by default when it is created but may be quieted to prevent the device identification string to be printed during probe. To quiet a... |
|
device_printf(9) -- formatted output conversion
|
|
The device_printf() function is a convenience interface to the printf(9) function. It outputs the name of the dev device, followed by a colon and a space, and then what printf(9) would print if you pa... |
|
DEVICE_PROBE(9) -- probe for device existence
|
|
This device method should probe to see if the device is present. It should return 0 if the device exists, ENXIO if it cannot be found. If some other error happens during the probe (such as a memory al... |
|
device_probe_and_attach(9) -- initialise a device
|
|
This function is called during autoconfiguration to initialise the devices in the system. For each device, the DEVICE_PROBE(9) method of each suitable driver is called and if a probe succeeds, a descr... |
|
device_quiet(9) -- manipulate device quiet flag
|
|
Each device has a quiet flag associated with it. A device is verbose by default when it is created but may be quieted to prevent the device identification string to be printed during probe. To quiet a... |
|
device_set_desc(9) -- access the description of a device
|
|
Manipulate the verbose description of a device. This description (if present) is printed as part of the message when it is attached during autoconfiguration. The variation device_set_desc_copy() is us... |
|
device_set_desc_copy(9) -- access the description of a device
|
|
Manipulate the verbose description of a device. This description (if present) is printed as part of the message when it is attached during autoconfiguration. The variation device_set_desc_copy() is us... |
|
device_set_driver(9) -- associate a specific driver with a device node in the tree
|
|
This function associates a specific driver with a given device node in the tree. It is typically used in DEVICE_IDENTIFY(9) functions to add devices to a bus that does not support doing so automatical... |
|
device_set_flags(9) -- manipulate driver flags
|
|
Each device supports a set of driver-dependent flags which are often used to control device behaviour. These flags are read by calling device_get_flags() and written by calling device_set_flags(). |
|
device_set_ivars(9) -- access bus private variables
|
|
The device_get_ivars() function returns the bus-specific instance variables of a device. The device_set_ivars() function sets the bus-specific instance variables of a device. Typically, only bus drive... |
|
DEVICE_SHUTDOWN(9) -- called during system shutdown
|
|
This is called during system shutdown to allow the driver to put the hardware into a consistent state for rebooting the computer. |
|
device_unbusy(9) -- manipulate device state
|
|
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY (described in device(9)). To test see if a device was successfully... |
|
device_verbose(9) -- manipulate device quiet flag
|
|
Each device has a quiet flag associated with it. A device is verbose by default when it is created but may be quieted to prevent the device identification string to be printed during probe. To quiet a... |
|
devstat(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
devstat_add_entry(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
devstat_end_transaction(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
devstat_remove_entry(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
devstat_start_transaction(9) -- kernel interface for keeping device statistics
|
|
The devstat subsystem is an interface for recording device statistics, as its name implies. The idea is to keep reasonably detailed statistics while utilizing a minimum amount of CPU time to record th... |
|
devsw(9) -- returns the cdevsw structure
|
|
The devsw() function returns a pointer to the cdevsw structure associated with this character device ID. If dev->si_cdevsw is set it is returned; otherwise, the major(9) offset into the cdevsw array i... |
|
devtoname(9) -- converts dev_t data into a string indicating the device name
|
|
The devtoname() function returns a pointer to the name of the device passed to it. The name is whatever was set to it in make_dev(). If no name is associated with dev, a pointer to a string consisting... |
|
dev_depends(9) -- manage dev_t's and DEVFS registration for devices
|
|
The make_dev() function creates a dev_t structure for a new device. If DEVFS is available, it is also notified of the presence of the new device. The device will be owned by uid, with the group owners... |
|
DEV_MODULE(9) -- device driver module declaration macro
|
|
The DEV_MODULE() macro declares a device driver kernel module. It fills in a moduledata_t structure and then calls DECLARE_MODULE() with the correct args, where name is the name of the module and evh ... |
|
disk(9) -- Kernel disk storage API
|
|
The disk storage API permits kernel device drivers providing access to disk-like storage devices to advertise the device to other kernel components, including GEOM(4), and devfs(5). Each disk device i... |
|
disk_create(9) -- Kernel disk storage API
|
|
The disk storage API permits kernel device drivers providing access to disk-like storage devices to advertise the device to other kernel components, including GEOM(4), and devfs(5). Each disk device i... |
|
disk_destroy(9) -- Kernel disk storage API
|
|
The disk storage API permits kernel device drivers providing access to disk-like storage devices to advertise the device to other kernel components, including GEOM(4), and devfs(5). Each disk device i... |
|
domain(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
DOMAIN_SET(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
driver(9) -- structure describing a device driver
|
|
Each driver in the kernel is described by a driver_t structure. The structure contains the name of the device, a pointer to a list of methods, an indication of the kind of device which the driver impl... |
|
DRIVER_MODULE(9) -- kernel driver declaration macro
|
|
The DRIVER_MODULE() macro declares a kernel driver. DRIVER_MODULE() expands to the real driver declaration, where the phrase name is used as the naming prefix for the driver and its functions. Note th... |
|
endtsleep(9) -- manage the queues of sleeping processes
|
|
The sleep queues used by msleep(9) and friends are stored in a hash array. The address of the wait channel is used to generate an index into the array. Each entry in the array is a queue of processes ... |
|
execsigs(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
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... |
|
fetch(9) -- fetch data from user-space
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
FREE(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
free(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
fubyte(9) -- fetch data from user-space
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuswintr(9) -- fetch data from user-space
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fusword(9) -- fetch data from user-space
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
fuword(9) -- fetch data from user-space
|
|
The fetch functions are designed to copy small amounts of data from userspace. The fetch routines provide the following functionality: fubyte() Fetches a byte of data from the user-space address base.... |
|
getmicrotime(9) -- get the current time
|
|
The microtime() and getmicrotime() functions store the system time as a struct timeval at the address specified by tv. The nanotime() and getnanotime() functions perform the same utility, but record t... |
|
getmicrouptime(9) -- get the time elapsed since boot
|
|
The microuptime() and getmicrouptime() functions store the time elapsed since boot as a struct timeval at the address specified by tv. The nanouptime() and getnanouptime() functions perform the same u... |
|
getnanotime(9) -- get the current time
|
|
The microtime() and getmicrotime() functions store the system time as a struct timeval at the address specified by tv. The nanotime() and getnanotime() functions perform the same utility, but record t... |
|
getnanouptime(9) -- get the time elapsed since boot
|
|
The microuptime() and getmicrouptime() functions store the time elapsed since boot as a struct timeval at the address specified by tv. The nanouptime() and getnanouptime() functions perform the same u... |
|
getnewvnode(9) -- get a new vnode
|
|
The getnewvnode() function initializes a new vnode, assigning it the vnode operations passed in vops. The vnode is either freshly allocated, or taken from the head of the free list depending on the nu... |
|
getpbuf(9) -- functions for managing physical buffers
|
|
These functions are used to allocate and release physical buffers. The physical buffers are allocated at system startup and are maintained in a separate pool from the main system buffers. They are int... |
|
get_cyclecount(9) -- get the CPU's fast counter register contents
|
|
The get_cyclecount() function uses a register available in most modern CPUs to return a value that is monotonically increasing inside each CPU. On SMP systems, there will be a number of separate monot... |
|
groupmember(9) -- checks group set for a group ID
|
|
The groupmember() function checks to see if the given gid is in the group set of the credentials. Its arguments are: gid The group ID to check for. cred The credentials to search for the group in. |
|
gsignal(9) -- post signal to a process or process group
|
|
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... |
|
htobe16(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
htobe32(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
htobe64(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
htole16(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
htole32(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
htole64(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
ifaddr(9) -- kernel interfaces for manipulating network interfaces
|
|
|
|
ifnet(9) -- kernel interfaces for manipulating network interfaces
|
|
|
|
ifqueue(9) -- kernel interfaces for manipulating network interfaces
|
|
|
|
if_data(9) -- kernel interfaces for manipulating network interfaces
|
|
|
|
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 obtained... |
|
intro(9) -- introduction to system kernel interfaces
|
|
This section contains information about the interfaces and subroutines in the kernel. |
|
issignal(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
ithread(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_add_handler(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_create(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_destroy(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_priority(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_remove_handler(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
ithread_schedule(9) -- kernel interrupt threads
|
|
Interrupt threads are kernel threads that run a list of handlers when triggered by either a hardware or software interrupt. Each interrupt handler has a name, handler function, handler argument, prior... |
|
jumbo(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_freem(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_pg_alloc(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_pg_free(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_pg_steal(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_phys_to_kva(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
jumbo_vm_init(9) -- kernel interface for allocating and
|
|
The jumbo buffer facility is designed for allocating disposable pagesized buffers. Buffers allocated via this facility can either be returned or not. This facility is primarily intended for use with n... |
|
KASSERT(9) -- kernel expression verification macro
|
|
In a kernel compiled with options INVARIANTS, the KASSERT() macro tests the given expression and if it is false, calls the panic(9) function, terminating the running system. In a kernel that does not ... |
|
kernacc(9) -- check memory regions for accessibility
|
|
The kernacc() and useracc() functions check whether operations of the type specified in rw are permitted in the range of virtual addresses given by addr and len. The possible values of rw are any bitw... |
|
killproc(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
kobj(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_class_compile(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_class_compile_static(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_class_free(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_create(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_delete(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kobj_init(9) -- a kernel object system for FreeBSD
|
|
The kernel object system implements an object-oriented programming system in the FreeBSD kernel. The system is based around the concepts of interfaces, which are descriptions of sets of methods; class... |
|
kproc_shutdown(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kproc_start(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread_create(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread_exit(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread_resume(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread_suspend(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
kthread_suspend_check(9) -- kernel threads
|
|
The function kproc_start() is used to start ``internal'' daemons such as bufdaemon, pagedaemon, vmdaemon, and the syncer and is intended to be called from SYSINIT(9). The udata argument is actually ... |
|
ktr(9) -- kernel tracing facility
|
|
KTR provides a circular buffer of events that can be logged in a printf(9) style fashion. These events can then be dumped either via ddb(4) or gdb(1). Events are created and logged in the kernel via t... |
|
le16dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le16enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le16toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le32dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le32enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le32toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le64dec(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le64enc(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
le64toh(9) -- byte order operations
|
|
The bswap16(), bswap32(), and bswap64() functions return a byte order swapped integer. On big endian systems, the number is converted to little endian byte order. On little endian systems, the number ... |
|
lock(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockcount(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockdestroy(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockinit(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockmgr(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockmgr_printinfo(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
lockstatus(9) -- lockmgr family of functions
|
|
The lockinit() function is used to initialize a lock. It must be called before any operation can be performed on a lock. Its arguments are: lkp A pointer to the lock to initialize. prio The priority p... |
|
mac(9) -- TrustedBSD Mandatory Access Control framework
|
|
Introduction The TrustedBSD mandatory access control framework permits dynamically introduced system security modules to modify system security functionality. This can be used to support a variety of ... |
|
major(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
make_dev(9) -- manage dev_t's and DEVFS registration for devices
|
|
The make_dev() function creates a dev_t structure for a new device. If DEVFS is available, it is also notified of the presence of the new device. The device will be owned by uid, with the group owners... |
|
make_dev_alias(9) -- manage dev_t's and DEVFS registration for devices
|
|
The make_dev() function creates a dev_t structure for a new device. If DEVFS is available, it is also notified of the presence of the new device. The device will be owned by uid, with the group owners... |
|
malloc(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
MALLOC(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
maybe_resched(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
mbchain(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mbpool(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_alloc(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_card_free(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_count(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_create(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_destroy(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_ext_free(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_free(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_get(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_get_keep(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbp_sync(9) -- Buffer pools for network interfaces
|
|
Mbuf pools are intented to help drivers for interface cards that need huge amounts of receive buffers and additionally provides a mapping between these buffers and 32-bit handles. An example of these ... |
|
mbuf(9) -- memory management in the kernel IPC subsystem
|
|
An mbuf is a basic unit of memory management in the kernel IPC subsystem. Network packets and socket buffers are stored in mbufs. A network packet may span multiple mbufs arranged into a mbuf chain (l... |
|
mb_detach(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_done(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_fixhdr(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_init(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_initm(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_int64be(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_int64le(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_mbuf(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_mem(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uint16be(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uint16le(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uint32be(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uint32le(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uint8(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_put_uio(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
mb_reserve(9) -- set of functions to build an mbuf chain from various data types
|
|
These functions are used to compose mbuf chains from various data types. The mbchain structure is used as a working context and should be initialized with a call to either mb_init() or mb_initm(). It ... |
|
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... |
|
mdchain(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_append_record(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_done(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_int64(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_int64be(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_int64le(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_mbuf(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_mem(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint16(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint16be(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint16le(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint32(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint32be(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint32le(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uint8(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_get_uio(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_initm(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
md_next_record(9) -- set of functions to dissect an mbuf chain to various data types
|
|
These functions are used to decompose mbuf chains to various data types. The mdchain structure is used as a working context and should be initialized through a call of the mb_initm() function. It has ... |
|
microseq(9) -- ppbus microsequencer developer's guide
|
|
See ppbus(4) for ppbus description and general info about the microsequencer. The purpose of this document is to encourage developers to use the microsequencer mechanism in order to have: 1. a uniform... |
|
microtime(9) -- get the current time
|
|
The microtime() and getmicrotime() functions store the system time as a struct timeval at the address specified by tv. The nanotime() and getnanotime() functions perform the same utility, but record t... |
|
microuptime(9) -- get the time elapsed since boot
|
|
The microuptime() and getmicrouptime() functions store the time elapsed since boot as a struct timeval at the address specified by tv. The nanouptime() and getnanouptime() functions perform the same u... |
|
minor(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
mi_switch(9) -- switch to another thread context
|
|
The mi_switch() function implements the machine independent prelude to a thread context switch. It is called from only a few distinguished places in the kernel code as a result of the principle of non... |
|
module(9) -- structure describing a kernel module
|
|
Each module in the kernel is described by a module_t structure. The structure contains the name of the device, a unique ID number, a pointer to an event handler function and to an argument, which is g... |
|
MODULE_DEPEND(9) -- set kernel module dependencies
|
|
The MODULE_DEPEND() macro sets a dependency on another kernel module with name moddepend, which has been registered its version with MODULE_VERSION(). Three versions must be specified on which the mod... |
|
MODULE_VERSION(9) -- set kernel module version
|
|
The MODULE_VERSION() macro sets the version of the module called name. Other kernel modules can then depend on this module (see MODULE_DEPEND(9)). |
|
mono_time(9) -- system time variables
|
|
The time variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated by the settimeofday(2) system call and by periodic clock interrupts. The boottime variable ho... |
|
msleep(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
mtx_assert(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_destroy(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_init(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_initialized(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_spin(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_lock_spin_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_owned(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_pool(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_alloc(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_create(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_destroy(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_find(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_lock(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_lock_spin(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_unlock(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_pool_unlock_spin(9) -- mutex pool routines
|
|
Mutex pools are designed to be used as short term leaf mutexes; i.e., the last mutex one might acquire before calling msleep(9). They operate using a shared pool of mutexes. A mutex may be chosen from... |
|
mtx_recursed(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
MTX_SYSINIT(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_trylock(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_trylock_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_unlock(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_unlock_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_unlock_spin(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
mtx_unlock_spin_flags(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
MULTI_DRIVER_MODULE(9) -- kernel driver declaration macro
|
|
The DRIVER_MODULE() macro declares a kernel driver. DRIVER_MODULE() expands to the real driver declaration, where the phrase name is used as the naming prefix for the driver and its functions. Note th... |
|
mutex(9) -- kernel synchronization primitives
|
|
Mutexes are the most basic and primary method of process synchronization. The major design considerations for mutexes are: 1. Acquiring and releasing uncontested mutexes should be as cheap as possible... |
|
namei(9) -- pathname translation and lookup operations
|
|
The namei facility allows the client to perform pathname translation and lookup operations. The namei functions will increment the reference count for the vnode in question. The reference count has to... |
|
nanotime(9) -- get the current time
|
|
The microtime() and getmicrotime() functions store the system time as a struct timeval at the address specified by tv. The nanotime() and getnanotime() functions perform the same utility, but record t... |
|
nanouptime(9) -- get the time elapsed since boot
|
|
The microuptime() and getmicrouptime() functions store the time elapsed since boot as a struct timeval at the address specified by tv. The nanouptime() and getnanouptime() functions perform the same u... |
|
NDFREE(9) -- pathname translation and lookup operations
|
|
The namei facility allows the client to perform pathname translation and lookup operations. The namei functions will increment the reference count for the vnode in question. The reference count has to... |
|
NDINIT(9) -- pathname translation and lookup operations
|
|
The namei facility allows the client to perform pathname translation and lookup operations. The namei functions will increment the reference count for the vnode in question. The reference count has to... |
|
net_add_domain(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
panic(9) -- bring down system on fatal error
|
|
The panic() function terminates the running system. The message fmt is a printf(3) style format string. The message is printed to the console and the location panicstr is set to the address of the mes... |
|
pbuf(9) -- functions for managing physical buffers
|
|
These functions are used to allocate and release physical buffers. The physical buffers are allocated at system startup and are maintained in a separate pool from the main system buffers. They are int... |
|
pci(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_disable_busmaster(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_disable_io(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_enable_busmaster(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_enable_io(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_find_bsf(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_find_device(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_get_powerstate(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_read_config(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_set_powerstate(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pci_write_config(9) -- PCI bus interface
|
|
The pci set of functions are used for managing PCI devices. The pci_read_config() function is used to read data from the PCI configuration space of the device dev, at offset reg, with width specifying... |
|
pfctlinput(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
pfctlinput2(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
pffindproto(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
pffindtype(9) -- network domain management
|
|
Network protocols installed in the system are maintained within what are called domains (for example the inetdomain and localdomain). struct domain { int dom_family; /* AF_xxx */ char *dom_name; void ... |
|
pfil(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_add_hook(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_hook_get(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfil_remove_hook(9) -- packet filter interface
|
|
The pfil framework allows for a specified function to be invoked for every incoming or outgoing packet for a particular network I/O stream. These hooks may be used to implement a firewall or perform p... |
|
pfind(9) -- locate a process by number
|
|
pfind() takes a pid as its argument and returns a pointer to the proc structure whose PID is specified in the argument only if the pid is on the allproc list. zpfind() takes a pid as its argument. If ... |
|
pgfind(9) -- locate a process group by number
|
|
The pgfind() function takes a pgid as its argument and returns a pointer to the pgrp structure whose pg_id is specified in the argument. pgfind() locks the pgrp structure that is returned. |
|
pgsigio(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
pgsignal(9) -- post signal to a process or process group
|
|
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
|
|
The physio() is a helper function typically called from character device read() and write() routines to start I/O on a user process buffer. The maximum amount of data to transfer with each call is det... |
|
pmap(9) -- machine-dependent portion of virtual memory subsystem
|
|
The pmap module is the machine-dependent portion of the FreeBSD VM (Virtual Memory) sub-system. Each function documented herein must have its own architecture-dependent implementation. The pmap module... |
|
pmap_activate(9) -- activate a physical map
|
|
The pmap_activate() function activates the physical map for a user thread td. This function must be called before the thread's address space may be accessed. |
|
pmap_addr_hint(9) -- get a hint for the best-fit mapping of a VM object
|
|
The pmap_addr_hint() function returns a hint for the best address at which to map the object obj at address addr of size bytes. |
|
pmap_change_wiring(9) -- change physical wiring for a map or virtual address pair
|
|
The pmap_change_wiring() function changes the wiring attribute for the page at virtual address va in the physical map pmap. A wired page gets its name from being `wired' into the system page tables s... |
|
pmap_clear_modify(9) -- set information about physical pages
|
|
The pmap_clear_modify() function clears the `modified' bit on the physical page m. The pmap_clear_reference() function clears the `referenced' bit on the physical page m. |
|
pmap_clear_reference(9) -- set information about physical pages
|
|
The pmap_clear_modify() function clears the `modified' bit on the physical page m. The pmap_clear_reference() function clears the `referenced' bit on the physical page m. |
|
pmap_copy(9) -- copy physical memory pages
|
|
The pmap_copy() function copies the range specified by src_addr and len from the source physical map src_pmap to the destination physical map dst_pmap at the address dst_addr. The pmap_copy_page() fun... |
|
pmap_copy_page(9) -- copy physical memory pages
|
|
The pmap_copy() function copies the range specified by src_addr and len from the source physical map src_pmap to the destination physical map dst_pmap at the address dst_addr. The pmap_copy_page() fun... |
|
pmap_enter(9) -- insert a virtual page into a physical map
|
|
The pmap_enter() function inserts the given physical page p, into the physical map pmap, at the virtual address va, with the protection prot. If wired is TRUE, then increment the wired count for the p... |
|
pmap_extract(9) -- map a virtual address to a physical page
|
|
The pmap_extract() function maps a virtual address to a physical page. In certain situations, callers may use pmap_extract_and_hold() instead, to ensure that the returned page is held. The pmap_extrac... |
|
pmap_extract_and_hold(9) -- map a virtual address to a physical page
|
|
The pmap_extract() function maps a virtual address to a physical page. In certain situations, callers may use pmap_extract_and_hold() instead, to ensure that the returned page is held. The pmap_extrac... |
|
pmap_growkernel(9) -- grow the kernel virtual address (KVA) space
|
|
The pmap_growkernel() function grows the kernel virtual address space to the virtual address addr. It will allocate more page entries if required. |
|
pmap_init(9) -- initialize the pmap subsystem
|
|
The pmap_init() function initializes the pmap(9) sub-system. It is called during system initialization by vm_init(), to initialize any structures that the pmap_init system needs in order to map betwee... |
|
pmap_init2(9) -- initialize the pmap subsystem
|
|
The pmap_init() function initializes the pmap(9) sub-system. It is called during system initialization by vm_init(), to initialize any structures that the pmap_init system needs in order to map betwee... |
|
pmap_is_modified(9) -- return information about physical pages
|
|
The pmap_is_modified() and pmap_ts_referenced() functions return information about physical pages. |
|
pmap_is_prefaultable(9) -- determine if a page may be prefaulted
|
|
The pmap_is_prefaultable() function provides a means of determining if the page residing at virtual address va in the physical map pmap may be pre-faulted into main memory. This is a helper function w... |
|
pmap_map(9) -- map a physical memory range into kernel virtual address (KVA) space
|
|
The pmap_map() function maps a range of physical addresses into kernel virtual address (KVA) space, from start to end, with protection bits prot. The value passed in *virt is treated as a hint for the... |
|
pmap_mincore(9) -- determine if a virtual address is resident in physical memory
|
|
The pmap_mincore() function determines if the page at the virtual address addr in the physical map pmap is resident in physical memory. It is the machine-dependent interface used by mincore(2) system ... |
|
pmap_object_init_pt(9) -- initialize page tables for a VM object
|
|
The pmap_object_init_pt() function preloads the page table entries into the specified physical map pmap, for the given object at the virtual address addr, for size bytes, beginning at the page index p... |
|
pmap_page_exists_quick(9) -- determine if a page exists in a physical map
|
|
The pmap_page_exists_quick() function is used to quickly determine if the page m exists in the physical map pmap. It is typically called from the VM paging code. |
|
pmap_page_protect(9) -- set physical page protection
|
|
The pmap_page_protect() function lowers the physical page permissions to prot for all mappings of a given page m. The pmap_protect() function sets the physical page permissions to prot for all physica... |
|
pmap_pinit(9) -- initialize pmap structures
|
|
The pmap_pinit() function initializes the preallocated and zeroed structure pmap, such as one in a vmspace structure. The pmap_pinit0() function initializes the physical map pm, associated with proces... |
|
pmap_pinit0(9) -- initialize pmap structures
|
|
The pmap_pinit() function initializes the preallocated and zeroed structure pmap, such as one in a vmspace structure. The pmap_pinit0() function initializes the physical map pm, associated with proces... |
|
pmap_pinit2(9) -- initialize pmap structures
|
|
The pmap_pinit() function initializes the preallocated and zeroed structure pmap, such as one in a vmspace structure. The pmap_pinit0() function initializes the physical map pm, associated with proces... |
|
pmap_protect(9) -- set physical page protection
|
|
The pmap_page_protect() function lowers the physical page permissions to prot for all mappings of a given page m. The pmap_protect() function sets the physical page permissions to prot for all physica... |
|
pmap_qenter(9) -- manage temporary kernel space mappings
|
|
The pmap_qenter() function accepts a linear array of count pointers to wired pages *m, and enters each of these pages into the kernel virtual address (KVA) space, beginning at the address sva. The pma... |
|
pmap_qremove(9) -- manage temporary kernel space mappings
|
|
The pmap_qenter() function accepts a linear array of count pointers to wired pages *m, and enters each of these pages into the kernel virtual address (KVA) space, beginning at the address sva. The pma... |
|
pmap_release(9) -- release resources held by a physical map
|
|
The pmap_release() function releases any resources held by the physical map pmap. This function is called when a pmap initialized by the corresponding function, pmap_pinit() is being released. |
|
pmap_remove(9) -- remove pages from a physical map
|
|
The pmap_remove() function removes the range of addresses between sva and eva from the physical map pmap. If eva is less than sva, then the result is undefined. It is assumed that both sva and eva are... |
|
pmap_remove_all(9) -- remove pages from a physical map
|
|
The pmap_remove() function removes the range of addresses between sva and eva from the physical map pmap. If eva is less than sva, then the result is undefined. It is assumed that both sva and eva are... |
|
pmap_remove_pages(9) -- remove pages from a physical map
|
|
The pmap_remove() function removes the range of addresses between sva and eva from the physical map pmap. If eva is less than sva, then the result is undefined. It is assumed that both sva and eva are... |
|
pmap_resident_count(9) -- return page resident and wiring statistics
|
|
The pmap_resident_count() and pmap_wired_count() macros allow pmap consumers to retrieve statistics from the pm_stats member of the machinedependent structure struct pmap. |
|
pmap_ts_modified(9) -- return information about physical pages
|
|
The pmap_is_modified() and pmap_ts_referenced() functions return information about physical pages. |
|
pmap_wired_count(9) -- return page resident and wiring statistics
|
|
The pmap_resident_count() and pmap_wired_count() macros allow pmap consumers to retrieve statistics from the pm_stats member of the machinedependent structure struct pmap. |
|
pmap_zero_area(9) -- zero-fill a page using
|
|
The pmap_zero_page() function zero-fills an entire page using machinedependent optimizations. The pmap_zero_page_area() function is used to zero-fill an area of a page. The range specified must not cr... |
|
pmap_zero_idle(9) -- zero-fill a page using
|
|
The pmap_zero_page() function zero-fills an entire page using machinedependent optimizations. The pmap_zero_page_area() function is used to zero-fill an area of a page. The range specified must not cr... |
|
pmap_zero_page(9) -- zero-fill a page using
|
|
The pmap_zero_page() function zero-fills an entire page using machinedependent optimizations. The pmap_zero_page_area() function is used to zero-fill an area of a page. The range specified must not cr... |
|
postsig(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
printf(9) -- formatted output conversion
|
|
The printf(9) family of functions are similar to the printf(3) family of functions. The three functions each use a different output stream. The uprintf() function outputs to the current process' cont... |
|
procrunnable(9) -- manage the queue of runnable processes
|
|
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. E... |
|
pseudofs(9) -- pseudo file system construction kit
|
|
The pseudofs module offers an abstract API for pseudo-file systems such as procfs(5) and linprocfs(5). It takes care of all the hairy bits like interfacing with the VFS system, enforcing access contro... |
|
psignal(9) -- post signal to a process or process group
|
|
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... |
|
random(9) -- supply pseudo-random numbers
|
|
The random() function will by default produce a sequence of numbers that can be duplicated by calling srandom() with `1' as the seed. The srandom() function may be called with any arbitrary seed valu... |
|
random_harvest(9) -- gather entropy from the kernel for the entropy device
|
|
The random_harvest() function is used by device drivers and other kernel processes to pass data that is considered (at least partially) stochastic to the entropy device. The caller should pass a point... |
|
read_random(9) -- supply pseudo-random numbers
|
|
The random() function will by default produce a sequence of numbers that can be duplicated by calling srandom() with `1' as the seed. The srandom() function may be called with any arbitrary seed valu... |
|
realloc(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
reallocf(9) -- kernel memory management routines
|
|
The malloc() function allocates uninitialized memory in kernel address space for an object whose size is specified by size. The free() function releases memory at address addr that was previously allo... |
|
relpbuf(9) -- functions for managing physical buffers
|
|
These functions are used to allocate and release physical buffers. The physical buffers are allocated at system startup and are maintained in a separate pool from the main system buffers. They are int... |
|
remrunqueue(9) -- manage the queue of runnable processes
|
|
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. E... |
|
resetpriority(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
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. |
|
resource_int_value(9) -- get a value from the hints mechanism
|
|
These functions fetch a value from the ``hints'' mechanism. The functions take the following arguments: name The name of the device to get the resource value from. unit The unit number of the device... |
|
resource_long_value(9) -- get a value from the hints mechanism
|
|
These functions fetch a value from the ``hints'' mechanism. The functions take the following arguments: name The name of the device to get the resource value from. unit The unit number of the device... |
|
resource_string_value(9) -- get a value from the hints mechanism
|
|
These functions fetch a value from the ``hints'' mechanism. The functions take the following arguments: name The name of the device to get the resource value from. unit The unit number of the device... |
|
rijndael(9) -- AES encryption
|
|
The rijndael_makeKey() function is used to set up the key schedule in key. The direction (which may be DIR_ENCRYPT or DIR_DECRYPT) specifies the intended use of the key. The length of the key (in bits... |
|
rman(9) -- resource management functions
|
|
The rman set of functions provides a flexible resource management abstraction. It is used extensively by the bus management code. It implements the abstractions of region and resource. A region descri... |
|
roundrobin(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
roundrobin_interval(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
rtalloc(9) -- look up a route in the kernel routing table
|
|
The kernel uses a radix tree structure to manage routes for the networking subsystem. The rtalloc() family of routines is used by protocols to query this structure for a route corresponding to a parti... |
|
rtalloc1(9) -- look up a route in the kernel routing table
|
|
The kernel uses a radix tree structure to manage routes for the networking subsystem. The rtalloc() family of routines is used by protocols to query this structure for a route corresponding to a parti... |
|
rtalloc_ign(9) -- look up a route in the kernel routing table
|
|
The kernel uses a radix tree structure to manage routes for the networking subsystem. The rtalloc() family of routines is used by protocols to query this structure for a route corresponding to a parti... |
|
rtentry(9) -- structure of an entry in the kernel routing table
|
|
The kernel provides a common mechanism by which all protocols can store and retrieve entries from a central table of routes. Parts of this mechanism are also used to interact with user-level processes... |
|
runqueue(9) -- manage the queue of runnable processes
|
|
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. E... |
|
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... |
|
sbuf(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_cat(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_clear(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_cpy(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_data(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_delete(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_finish(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_len(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_new(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_overflowed(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_printf(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_putc(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_setpos(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_trim(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
sbuf_vprintf(9) -- safe string formatting
|
|
The sbuf family of functions allows one to safely allocate, construct and release bounded null-terminated strings in kernel space. Instead of arrays of characters, these functions operate on structure... |
|
schedclock(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
schedcpu(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
scheduler(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
sched_setup(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
selrecord(9) -- record and wakeup select requests
|
|
selrecord() and selwakeup() are the two central functions used by select(2), poll(2) and the objects that are being selected on. They handle the task of recording which threads are waiting on which ob... |
|
selwakeup(9) -- record and wakeup select requests
|
|
selrecord() and selwakeup() are the two central functions used by select(2), poll(2) and the objects that are being selected on. They handle the task of recording which threads are waiting on which ob... |
|
sema(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_destroy(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_init(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_post(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_timedwait(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_trywait(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_value(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
sema_wait(9) -- kernel counting semaphore
|
|
Counting semaphores provide a mechanism for synchronizing access to a pool of resources. Unlike mutexes, semaphores do not have the concept of an owner, so they can also be useful in situations where ... |
|
setrunnable(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
setrunqueue(9) -- manage the queue of runnable processes
|
|
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. E... |
|
SETSETNEQ(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SETSETOR(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGADDSET(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGDELSET(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGEMPTYSET(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
sigexit(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGFILLSET(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
siginit(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGISEMPTY(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGISMEMBER(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
signal(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGNOTEMPTY(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
signotify(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGPENDING(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGSETAND(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGSETCANTMASK(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGSETEQ(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIGSETNAND(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIG_CONTSIGMASK(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
SIG_STOPSIGMASK(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
sleep(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
sleepinit(9) -- manage the queues of sleeping processes
|
|
The sleep queues used by msleep(9) and friends are stored in a hash array. The address of the wait channel is used to generate an index into the array. Each entry in the array is a queue of processes ... |
|
sleepqueue(9) -- manage the queues of sleeping processes
|
|
The sleep queues used by msleep(9) and friends are stored in a hash array. The address of the wait channel is used to generate an index into the array. Each entry in the array is a queue of processes ... |
|
spl(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
spl0(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splbio(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splclock(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splhigh(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splimp(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splnet(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splsoftclock(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splsofttty(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splstatclock(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
spltty(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splvm(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
splx(9) -- manipulate interrupt priorities
|
|
This API is deprecated. Use mutexes to protect data structures instead. See mutex(9) for more information. The spl() function family sets the interrupt priority ``level'' of the CPU. This prevents i... |
|
srandom(9) -- supply pseudo-random numbers
|
|
The random() function will by default produce a sequence of numbers that can be duplicated by calling srandom() with `1' as the seed. The srandom() function may be called with any arbitrary seed valu... |
|
store(9) -- store data to user-space
|
|
The store functions are designed to copy small amounts of data to userspace. The store routines provide the following functionality: subyte() Stores a byte of data to the user-space address base. susw... |
|
style(9) -- kernel source file style guide
|
|
This file specifies the preferred style for kernel source files in the FreeBSD source tree. It is also a guide for the preferred userland code style. Many of the style rules are implicit in the exampl... |
|
subyte(9) -- store data to user-space
|
|
The store functions are designed to copy small amounts of data to userspace. The store routines provide the following functionality: subyte() Stores a byte of data to the user-space address base. susw... |
|
suser(9) -- check if process has superuser privilege
|
|
The suser and suser_cred functions check if the credentials given include superuser powers. The suser function is the most common, and should be used unless special circumstances dictate otherwise. Th... |
|
suser_cred(9) -- check if process has superuser privilege
|
|
The suser and suser_cred functions check if the credentials given include superuser powers. The suser function is the most common, and should be used unless special circumstances dictate otherwise. Th... |
|
suswintr(9) -- store data to user-space
|
|
The store functions are designed to copy small amounts of data to userspace. The store routines provide the following functionality: subyte() Stores a byte of data to the user-space address base. susw... |
|
susword(9) -- store data to user-space
|
|
The store functions are designed to copy small amounts of data to userspace. The store routines provide the following functionality: subyte() Stores a byte of data to the user-space address base. susw... |
|
suword(9) -- store data to user-space
|
|
The store functions are designed to copy small amounts of data to userspace. The store routines provide the following functionality: subyte() Stores a byte of data to the user-space address base. susw... |
|
swi(9) -- register and schedule software interrupt handlers
|
|
These functions are used to register and schedule software interrupt handlers. Software interrupt handlers are attached to a software interrupt thread, just as hardware interrupt handlers are attached... |
|
swi_add(9) -- register and schedule software interrupt handlers
|
|
These functions are used to register and schedule software interrupt handlers. Software interrupt handlers are attached to a software interrupt thread, just as hardware interrupt handlers are attached... |
|
swi_sched(9) -- register and schedule software interrupt handlers
|
|
These functions are used to register and schedule software interrupt handlers. Software interrupt handlers are attached to a software interrupt thread, just as hardware interrupt handlers are attached... |
|
sx(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_assert(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_destroy(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_downgrade(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_init(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_slock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_sunlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
SX_SYSINIT(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_slock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_upgrade(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_try_xlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_xlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
sx_xunlock(9) -- kernel shared/exclusive lock
|
|
Shared/exclusive locks are used to protect data that are read far more often than they are written. Mutexes are inherently more efficient than shared/exclusive locks, so shared/exclusive locks should ... |
|
SYSCALL_MODULE(9) -- syscall kernel module declaration macro
|
|
The SYSCALL_MODULE() macro declares a new syscall. SYSCALL_MODULE() expands into a kernel module declaration named as name. offset is a pointer to an int which saves the offset in struct sysent where ... |
|
SYSCTL_ADD_INT(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_LONG(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_NODE(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
sysctl_add_oid(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_OID(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_OPAQUE(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_PROC(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_STRING(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_STRUCT(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_UINT(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
SYSCTL_ADD_ULONG(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
sysctl_ctx_entry_add(9) -- sysctl context for managing dynamically created sysctl oids
|
|
These functions provide an interface for managing dynamically created oids. The sysctl context is responsible for keeping track of created oids, as well as their proper removal when needed. It adds a ... |
|
sysctl_ctx_entry_del(9) -- sysctl context for managing dynamically created sysctl oids
|
|
These functions provide an interface for managing dynamically created oids. The sysctl context is responsible for keeping track of created oids, as well as their proper removal when needed. It adds a ... |
|
sysctl_ctx_entry_find(9) -- sysctl context for managing dynamically created sysctl oids
|
|
These functions provide an interface for managing dynamically created oids. The sysctl context is responsible for keeping track of created oids, as well as their proper removal when needed. It adds a ... |
|
sysctl_ctx_free(9) -- sysctl context for managing dynamically created sysctl oids
|
|
These functions provide an interface for managing dynamically created oids. The sysctl context is responsible for keeping track of created oids, as well as their proper removal when needed. It adds a ... |
|
sysctl_ctx_init(9) -- sysctl context for managing dynamically created sysctl oids
|
|
These functions provide an interface for managing dynamically created oids. The sysctl context is responsible for keeping track of created oids, as well as their proper removal when needed. It adds a ... |
|
sysctl_remove_oid(9) -- runtime sysctl tree manipulation
|
|
These functions and macros provide an interface for creating and deleting sysctl oids at runtime (e.g. during lifetime of a module). The alternative method, based on linker sets (see |
|
taskqueue(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
taskqueue_create(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
TASKQUEUE_DECLARE(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
TASKQUEUE_DEFINE(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
taskqueue_enqueue(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
taskqueue_find(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
taskqueue_free(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
taskqueue_run(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
TASK_INIT(9) -- asynchronous task execution
|
|
These functions provide a simple interface for asynchronous execution of code. The function taskqueue_create() is used to create new queues. The arguments to taskqueue_create() include a name which sh... |
|
thread_exit(9) -- abandon current thread context
|
|
The thread_exit() function implements the machine independent prelude to a thread shutdown. It will not return, and will result in a call to mi_switch(9) to schedule some other thread. thread_exit() a... |
|
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 length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
tprintf(9) -- formatted output conversion
|
|
The printf(9) family of functions are similar to the printf(3) family of functions. The three functions each use a different output stream. The uprintf() function outputs to the current process' cont... |
|
trapsignal(9) -- kernel signal functions
|
|
The SIGADDSET() macro adds signo to set. No effort is made to ensure that signo is a valid signal number. The SIGDELSET() macro removes signo from set. No effort is made to ensure that signo is a vali... |
|
trypbuf(9) -- functions for managing physical buffers
|
|
These functions are used to allocate and release physical buffers. The physical buffers are allocated at system startup and are maintained in a separate pool from the main system buffers. They are int... |
|
tsleep(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
tvtohz(9) -- convert time interval to tick count
|
|
The tvtohz() function accepts a single argument tv which specifies the time interval over which to calculate the number of system ticks that would elapse. |
|
ucred(9) -- functions related to user credentials
|
|
The ucred family of functions is used to manage user credential structures (struct ucred) within the kernel. The crget() function allocates memory for a new structure, sets its reference count to 1, a... |
|
uidinfo(9) -- functions for managing UID information
|
|
The uidinfo family of functions is used to manage uidinfo structures. Each uidinfo structure maintains per uid resource consumption counts, including the process count and socket buffer space usage. T... |
|
uifind(9) -- functions for managing UID information
|
|
The uidinfo family of functions is used to manage uidinfo structures. Each uidinfo structure maintains per uid resource consumption counts, including the process count and socket buffer space usage. T... |
|
uifree(9) -- functions for managing UID information
|
|
The uidinfo family of functions is used to manage uidinfo structures. Each uidinfo structure maintains per uid resource consumption counts, including the process count and socket buffer space usage. T... |
|
uihashinit(9) -- functions for managing UID information
|
|
The uidinfo family of functions is used to manage uidinfo structures. Each uidinfo structure maintains per uid resource consumption counts, including the process count and socket buffer space usage. T... |
|
uihold(9) -- functions for managing UID information
|
|
The uidinfo family of functions is used to manage uidinfo structures. Each uidinfo structure maintains per uid resource consumption counts, including the process count and socket buffer space usage. T... |
|
uio(9) -- device driver I/O routines
|
|
The function uiomove() is used to handle transfer of data between buffers and I/O vectors that might possibly also cross the user/kernel space boundary. As a result of any read(2), write(2), readv(2),... |
|
uiomove(9) -- device driver I/O routines
|
|
The function uiomove() is used to handle transfer of data between buffers and I/O vectors that might possibly also cross the user/kernel space boundary. As a result of any read(2), write(2), readv(2),... |
|
uma(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
umajor(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
uma_zalloc(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
uma_zcreate(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
uma_zdestroy(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
uma_zfree(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
uma_zone_set_max(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
uminor(9) -- calculate device ids
|
|
The device_ids family of functions take either the raw device ID, id, or a pointer to the device structure, dev, and return the integer value that is the major or minor device ID as requested. The act... |
|
unsleep(9) -- manage the queues of sleeping processes
|
|
The sleep queues used by msleep(9) and friends are stored in a hash array. The address of the wait channel is used to generate an index into the array. Each entry in the array is a queue of processes ... |
|
untimeout(9) -- execute a function after a specified length of time
|
|
The function timeout() schedules a call to the function given by the argument func to take place after ticks/hz seconds. Non-positive values of ticks are silently converted to the value `1'. func sho... |
|
updatepri(9) -- perform round-robin scheduling of runnable processes
|
|
Each process has three different priorities stored in struct proc: p_usrpri, p_nativepri, and p_priority. The p_usrpri member is the user priority of the process calculated from a process' estimated ... |
|
uprintf(9) -- formatted output conversion
|
|
The printf(9) family of functions are similar to the printf(3) family of functions. The three functions each use a different output stream. The uprintf() function outputs to the current process' cont... |
|
useracc(9) -- check memory regions for accessibility
|
|
The kernacc() and useracc() functions check whether operations of the type specified in rw are permitted in the range of virtual addresses given by addr and len. The possible values of rw are any bitw... |
|
utopia(9) -- Driver module for ATM PHY chips
|
|
This module is used by all ATM drivers for cards that use a number of known PHY chips to provide uniform functionality. The module implements status monitoring in either interrupt or polling mode, med... |
|
vaccess(9) -- generate an access control decision using vnode parameters
|
|
This call implements the logic for the UNIX discretionary file security model common to many file systems in FreeBSD. It accepts the vnodes type type, permissions via file_mode, owning UID file_uid, o... |
|
vaccess_acl_posix1e(9) -- generate a POSIX.1e ACL access control decision using vnode parameters
|
|
This call implements the logic for the UNIX discretionary file security model with POSIX.1e ACL extensions. It accepts the vnodes type type, owning UID file_uid, owning GID file_gid, access ACL for th... |
|
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. count_dev() does the same thing as vcount(), but tak... |
|
vdrop(9) -- acquire/release 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 is still referenced, it will be removed. The vdrop() function decrements the ... |
|
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. rootrefs The number of refer... |
|
VFS(9) -- kernel interface to file systems
|
|
Calls used to set or query file systems for settings or information. File systems that don't implement a VFS operation should use the appropriate vfs_std function from src/sys/kern/vfs_default.c rath... |
|
vfsconf(9) -- vfs configuration information
|
|
Each file system type known to the kernel has a vfsconf structure that contains the information required to create a new mount of that file systems type. struct vfsconf { struct vfsops *vfc_vfsops; /*... |
|
vfs_busy(9) -- marks a mount point as busy
|
|
The vfs_busy() function marks a mount point as busy. The purpose of this function is to synchronize access to a mount point. It also delays unmounting by sleeping on mp if the MNTK_UNMOUNT flag is set... |
|
VFS_CHECKEXP(9) -- check if a file system is exported to a client
|
|
This is used by the NFS server to check if a mount point is exported to a client. Its arguments are: mp The mount point to be checked. nam An mbuf containing the network address of the client. exflags... |
|
VFS_FHTOVP(9) -- turn an NFS filehandle into a vnode
|
|
This is used by the NFS server to turn an NFS filehandle into a vnode. Its arguments are: mp The file system. fhp The filehandle to convert. vpp Return parameter for the new locked vnode. The contents... |
|
vfs_getnewfsid(9) -- allocate a new file system identifier
|
|
The vfs_getnewfsid() function allocates a new file system identifier for the mount point given. File systems typically call vfs_getnewfsid() in their mount routine in order to acquire a unique ID with... |
|
vfs_getvfs(9) -- returns a mount point given its file system identifier
|
|
The vfs_getvfs() function returns the mount point structure for a file system given its file system identifier. The file system ID should have been allocated by calling vfs_getnewfsid(9); otherwise, i... |
|
VFS_INIT(9) -- initialize a file system
|
|
This function is called once to allow a file system to initialize any global data structures that it might have. It is either called when the operating system boots or, for dynamically loaded file sys... |
|
vfs_modevent(9) -- vfs configuration information
|
|
Each file system type known to the kernel has a vfsconf structure that contains the information required to create a new mount of that file systems type. struct vfsconf { struct vfsops *vfc_vfsops; /*... |
|
VFS_MOUNT(9) -- mount a file system
|
|
Mount a file system into the system's namespace. Its arguments are: mp Structure representing the file system. path Pathname where the file system is being mounted. data File system specific data. Th... |
|
vfs_mount(9) -- generic file system mount function
|
|
The vfs_mount() function handles the generic portion of mounting a file system, and calls the file system specific mount function after verifying its parameters and setting up the structures expected ... |
|
vfs_mountedon(9) -- check if the vnode belongs to a mounted file system
|
|
vfs_mountedon() inspects the mount structure in vp to determine if it points to a valid mount point. If the mount is valid, the vnode is considered to be busy. A common use of vfs_mountedon() is to ca... |
|
VFS_QUOTACTL(9) -- manipulate file system quotas
|
|
Implement file system quotas. See quotactl(2) for a description of the arguments. |
|
vfs_register(9) -- vfs configuration information
|
|
Each file system type known to the kernel has a vfsconf structure that contains the information required to create a new mount of that file systems type. struct vfsconf { struct vfsops *vfc_vfsops; /*... |
|
VFS_ROOT(9) -- return the root vnode of a file system
|
|
Return a locked vnode for the root directory of the file system. Its arguments are: mp The file system. vpp Return parameter for the root vnode. |
|
vfs_rootmountalloc(9) -- allocate a root mount structure
|
|
vfs_rootmountalloc() allocates a mount structure initialized from the vfsconf type that matches fstypename. |
|
VFS_SET(9) -- set up loadable file system vfsconf
|
|
VFS_SET() creates a vfsconf structure for the loadable module with the given vfsops, fsname and flags, and declares it by calling DECLARE_MODULE(9) using vfs_modevent() as the event handler. Possible ... |
|
VFS_START(9) -- make a file system operational
|
|
This is called after VFS_MOUNT(9) and before the first access to the file system. Its arguments are: mp The file system. flags ?? td Thread which is starting the file system. |
|
VFS_STATFS(9) -- return file system status
|
|
This call returns various pieces of information about the file system, including recommended I/O sizes, free space, free inodes, etc. Its arguments are: mp The file system. sbp Return parameter for th... |
|
VFS_SYNC(9) -- flush unwritten data
|
|
This writes out all unwritten data in a file system. Its arguments are: mp The file system. waitfor Whether the function should wait for I/O to complete. Possible values are: MNT_WAIT synchronously wa... |
|
vfs_timestamp(9) -- generate current timestamp
|
|
The vfs_timestamp() function fills in tsp with the current time. The precision is based on the value of the vfs.timestamp_precision sysctl variable: 0 seconds only; nanoseconds are zeroed. 1 seconds a... |
|
vfs_unbusy(9) -- unbusy a mount point
|
|
The vfs_unbusy() function un-busies a mount point by unlocking mp->mnt_lock. The lock is typically acquired by calling vfs_busy(9) prior to this call. Its arguments are: mp The mount point to unbusy (... |
|
VFS_UNMOUNT(9) -- unmount a file system
|
|
Unmount a file system. Its arguments are: mp The file system. mntflags Various flags. td Thread which is unmounting the file system. If the MNT_FORCE flag is specified then open files should be forcib... |
|
vfs_unmountall(9) -- unmount all file systems
|
|
The vfs_unmountall function, run only at system shutdown, unmounts all mounted file systems from most recent to oldest in order to avoid handling dependencies. |
|
vfs_unregister(9) -- vfs configuration information
|
|
Each file system type known to the kernel has a vfsconf structure that contains the information required to create a new mount of that file systems type. struct vfsconf { struct vfsops *vfc_vfsops; /*... |
|
VFS_VGET(9) -- convert an inode number to a vnode
|
|
This converts an inode number into a locked vnode. Its arguments are: mp The file system. ino The inode representing the file. flags Additional locking flags to pass through. vpp Return parameter for ... |
|
VFS_VPTOFH(9) -- turn a vnode into an NFS filehandle
|
|
This is used by the NFS server to create an opaque filehandle which uniquely identifies the file and which can be used by an NFS client to access the file in the future. Its arguments are: vp The vnod... |
|
vget(9) -- get a vnode from the free list
|
|
Get a vnode from the free list and increment its reference count. vp the vnode to remove from the free list lockflag if non-zero, the vnode will also be locked When not in use, vnodes are kept on a fr... |
|
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. If the vn... |
|
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. If the vn... |
|
vhold(9) -- acquire/release 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 is still referenced, it will be removed. The vdrop() function decrements the ... |
|
vinvalbuf(9) -- flushes and invalidates 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... |
|
vm_fault_prefault(9) -- cluster page faults into a process's address space
|
|
The vm_map_prefault() function provides a means of clustering pagefaults into a process's address space. It operates upon the physical map pmap. The entry argument specifies the entry to be prefaulte... |
|
vm_map(9) -- virtual address space portion of virtual memory subsystem
|
|
The vm_map subsystem is used to manage virtual address spaces. This section describes the main data structures used within the code. The struct vm_map is a generic representation of an address space. ... |
|
vm_map_check_protection(9) -- check memory protection for a vm_map
|
|
The vm_map_check_protection() function asserts that the target map allows the specified privilege protection over the entire address range from start to end. The region MUST be contiguous; no holes ar... |
|
vm_map_clean(9) -- push dirty pages to their pager
|
|
The vm_map_clean() function forces any dirty cached pages in the range start to end within the map to be pushed to their underlying pager. If syncio is TRUE, dirty pages are written synchronously. If ... |
|
vm_map_create(9) -- create a new vm_map structure
|
|
The vm_map_create() function creates and returns a new, empty map structure, associated with the physical map pmap, and with the upper and lower address bounds specified by max and min respectively. |
|
vm_map_delete(9) -- deallocate an address range from a map
|
|
The vm_map_delete() function deallocates the address range bounded by start and end from the map. |
|
vm_map_find(9) -- find a free region within a map, and optionally map a vm_object
|
|
The vm_map_find() function attempts to find a free region in the target map, with the given length, and will also optionally create a mapping of object. The arguments offset, prot, max, and cow are pa... |
|
vm_map_findspace(9) -- find a free region within a map
|
|
The vm_map_findspace() function attempts to find a region with sufficient space in the map for an object of size length at the address addr. |
|
vm_map_growstack(9) -- manage process stacks
|
|
The function maps a process stack for a new process image. The stack is mapped addrbos in map, with a maximum size of max_ssize. Copy-on-write flags passed in cow are also applied to the new mapping. ... |
|
vm_map_inherit(9) -- set fork inheritance flags for a range within a map
|
|
The vm_map_inherit() function sets the inheritance flags for the range start to end within the target map to the value new_inheritance. The new_inheritance flag must have one of the values VM_INHERIT_... |
|
vm_map_init(9) -- initialize a vm_map structure for process zero
|
|
The vm_map_init() function initializes the system map map by setting its upper and lower address bounds to max and min respectively. It also initializes the system map mutex. |
|
vm_map_insert(9) -- insert an object into a map
|
|
The vm_map_insert() function inserts a mapping for the entire vm_object object into the target map map. The offset argument specifies the offset into the object at which to begin mapping. The object'... |
|
vm_map_lock(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_lock_downgrade(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_lock_read(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_lock_upgrade(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_lookup(9) -- lookup the vm_object backing a given virtual region
|
|
The vm_map_lookup() function attempts to find the vm_object, page index and protection, for the given virtual address vaddr, in the map var_map, assuming a page fault of the type fault_type had occurr... |
|
vm_map_lookup_done(9) -- lookup the vm_object backing a given virtual region
|
|
The vm_map_lookup() function attempts to find the vm_object, page index and protection, for the given virtual address vaddr, in the map var_map, assuming a page fault of the type fault_type had occurr... |
|
vm_map_madvise(9) -- apply advice about use of memory to map entries
|
|
The vm_map_madvise() function applies the flags behav to the entries within map between start and end. Advisories are classified as either those affecting the vm_map_entry structure, or those affectin... |
|
vm_map_max(9) -- return map properties
|
|
The function vm_map_max() returns the upper address bound of the map map. The function vm_map_min() returns the lower address bound of the map map. The function vm_map_pmap() returns a pointer to the ... |
|
vm_map_min(9) -- return map properties
|
|
The function vm_map_max() returns the upper address bound of the map map. The function vm_map_min() returns the lower address bound of the map map. The function vm_map_pmap() returns a pointer to the ... |
|
vm_map_pmap(9) -- return map properties
|
|
The function vm_map_max() returns the upper address bound of the map map. The function vm_map_min() returns the lower address bound of the map map. The function vm_map_pmap() returns a pointer to the ... |
|
vm_map_protect(9) -- apply protection bits to a virtual memory region
|
|
The vm_map_protect() function sets the protection bits of the address region bounded by start and end within the map map to new_prot. If set_max is TRUE, new_prot is treated as the new max_protection ... |
|
vm_map_remove(9) -- remove a virtual address range from a map
|
|
The vm_map_remove() function removes the given address range bounded by start and end from the target map. |
|
vm_map_simplify_entry(9) -- simplify a vm_map_entry
|
|
The vm_map_simplify_entry() function simplifies the given entry by merging with either neighbour. The map must be locked upon entry. This function also has the ability to merge with both neighbours. T... |
|
vm_map_stack(9) -- manage process stacks
|
|
The function maps a process stack for a new process image. The stack is mapped addrbos in map, with a maximum size of max_ssize. Copy-on-write flags passed in cow are also applied to the new mapping. ... |
|
vm_map_submap(9) -- create a subordinate map
|
|
The vm_map_submap() function marks the range bounded by start and end within the map map as being handled by a subordinate map sub_map. It is generally called by the kernel memory allocator. |
|
vm_map_trylock(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_trylock_read(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_unlock(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_unlock_read(9) -- vm_map locking macros
|
|
The vm_map_lock() macro obtains an exclusive lock on map. The vm_map_unlock() macro releases an exclusive lock on map. The vm_map_lock_read() macro obtains a read-lock on map. Currently this is implem... |
|
vm_map_unwire(9) -- manage page wiring within a virtual memory map
|
|
The vm_map_wire() function is responsible for wiring pages in the range between start and end within the map map. Wired pages are locked into physical memory, and may not be paged out as long as their... |
|
vm_map_wire(9) -- manage page wiring within a virtual memory map
|
|
The vm_map_wire() function is responsible for wiring pages in the range between start and end within the map map. Wired pages are locked into physical memory, and may not be paged out as long as their... |
|
vm_page_alloc(9) -- allocate a page for a vm_object
|
|
The vm_page_alloc() function allocates a page at pindex within object. It is assumed that a page has not already been allocated at pindex. The page returned is inserted into the object, but is not ins... |
|
vm_page_bits(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_busy(9) -- handle the busying and unbusying of a page
|
|
These functions handle the busying, unbusying and notification of the unbusying of a page. vm_page_busy() sets the PG_BUSY flag in the page. vm_page_flash() checks to see if there is anybody waiting o... |
|
vm_page_cache(9) -- move a page onto the cache queue
|
|
The vm_page_cache() function moves a page onto the cache queue, and removes any protection that may be set on the page. If the page is busy, wired or unmanaged then the move to the cache queue will fa... |
|
vm_page_clear_dirty(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_copy(9) -- copy a page
|
|
The vm_page_copy() function copies the contents of src_m into dst_m. The entire contents of dst_m are marked as valid. The actual copy is performed by pmap_copy_page(). |
|
vm_page_deactivate(9) -- deactivate a page
|
|
The vm_page_deactivate() function moves the given page to the inactive queue as long as it is unmanaged and is not wired. |
|
vm_page_dirty(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_dontneed(9) -- indicate that a page is not needed anymore
|
|
The vm_page_dontneed() function advises the VM system that the given page is no longer required. If the page is already in the inactive queue or in the cache queue, this function does nothing; otherwi... |
|
vm_page_flag(9) -- change page flags
|
|
The vm_page_flag_clear() atomically clears the specified bits on the page's flags. The vm_page_flag_set() atomically sets the specified bits on the page's flags. The functions arguments are: m The p... |
|
vm_page_flag_clear(9) -- change page flags
|
|
The vm_page_flag_clear() atomically clears the specified bits on the page's flags. The vm_page_flag_set() atomically sets the specified bits on the page's flags. The functions arguments are: m The p... |
|
vm_page_flag_set(9) -- change page flags
|
|
The vm_page_flag_clear() atomically clears the specified bits on the page's flags. The vm_page_flag_set() atomically sets the specified bits on the page's flags. The functions arguments are: m The p... |
|
vm_page_flash(9) -- handle the busying and unbusying of a page
|
|
These functions handle the busying, unbusying and notification of the unbusying of a page. vm_page_busy() sets the PG_BUSY flag in the page. vm_page_flash() checks to see if there is anybody waiting o... |
|
vm_page_free(9) -- free a page
|
|
The vm_page_free_toq() function moves a page into the free queue, and disassociates it from its object. If the page is held, wired, already free, or its busy count is not zero, the system will panic. ... |
|
vm_page_free_toq(9) -- free a page
|
|
The vm_page_free_toq() function moves a page into the free queue, and disassociates it from its object. If the page is held, wired, already free, or its busy count is not zero, the system will panic. ... |
|
vm_page_free_zero(9) -- free a page
|
|
The vm_page_free_toq() function moves a page into the free queue, and disassociates it from its object. If the page is held, wired, already free, or its busy count is not zero, the system will panic. ... |
|
vm_page_grab(9) -- returns a page from an object
|
|
The vm_page_grab() function returns the page at pindex from the given object. If the page exists and is busy, vm_page_grab() will sleep while waiting for it. If the page does not exist, it is allocate... |
|
vm_page_hold(9) -- update a page's hold count
|
|
The vm_page_hold() function increases the hold count on a page. This prevents the page daemon from freeing the page. vm_page_hold() should only be used for very temporary wiring of a page, as that pag... |
|
vm_page_insert(9) -- add/remove page from an object
|
|
The vm_page_insert() function adds a page to the given object at the given index. The page is added to both the VM page hash table and to the object's list of pages, but the hardware page tables are ... |
|
vm_page_io(9) -- ready or unready a page for I/O
|
|
The vm_page_io_start() function prepares the page for I/O by incrementing its busy flag by 1. The vm_page_io_finish() function lowers the busy count on the page by one, if the resulting busy count is ... |
|
vm_page_io_finish(9) -- ready or unready a page for I/O
|
|
The vm_page_io_start() function prepares the page for I/O by incrementing its busy flag by 1. The vm_page_io_finish() function lowers the busy count on the page by one, if the resulting busy count is ... |
|
vm_page_io_start(9) -- ready or unready a page for I/O
|
|
The vm_page_io_start() function prepares the page for I/O by incrementing its busy flag by 1. The vm_page_io_finish() function lowers the busy count on the page by one, if the resulting busy count is ... |
|
vm_page_is_valid(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_lookup(9) -- lookup a vm page
|
|
The vm_page_lookup() function searches for a VM page given its VM object and index. If the page is not found, NULL is returned. Its arguments are: object The VM object to search on. pindex The page in... |
|
vm_page_protect(9) -- lower a page's protection
|
|
The vm_page_protect() function lowers a page's protection. The protection is never raised by this function; therefore, if the page is already at VM_PROT_NONE, the function does nothing. Its arguments... |
|
vm_page_remove(9) -- add/remove page from an object
|
|
The vm_page_insert() function adds a page to the given object at the given index. The page is added to both the VM page hash table and to the object's list of pages, but the hardware page tables are ... |
|
vm_page_rename(9) -- move a page
|
|
The vm_page_rename() function removes a page from one object, and adds it to another at the given page index. The page is added to the given object, and is removed from the object that is currently as... |
|
vm_page_set_invalid(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_set_validclean(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_sleep_busy(9) -- wait for a busy page to become unbusy
|
|
The vm_page_sleep_busy() function waits until the PG_BUSY flag is cleared. If also_m_busy is non-zero, it also waits for m->busy to become zero. |
|
vm_page_test_dirty(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_try_to_free(9) -- free a page
|
|
The vm_page_free_toq() function moves a page into the free queue, and disassociates it from its object. If the page is held, wired, already free, or its busy count is not zero, the system will panic. ... |
|
vm_page_undirty(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_page_unhold(9) -- update a page's hold count
|
|
The vm_page_hold() function increases the hold count on a page. This prevents the page daemon from freeing the page. vm_page_hold() should only be used for very temporary wiring of a page, as that pag... |
|
vm_page_unmanage(9) -- make a page unmanaged
|
|
The vm_page_unmanage() function flags that the page should no longer be managed by the VM system like other pages. The page is removed from any page queue it may be on, and after its PG_UNMANAGED flag... |
|
vm_page_unwire(9) -- wire and unwire pages
|
|
The vm_page_wire() function increments the wire count on a page, and removes it from whatever queue it is on. The vm_page_unwire() function releases one of the wirings on the page. When write_count re... |
|
vm_page_wakeup(9) -- handle the busying and unbusying of a page
|
|
These functions handle the busying, unbusying and notification of the unbusying of a page. vm_page_busy() sets the PG_BUSY flag in the page. vm_page_flash() checks to see if there is anybody waiting o... |
|
vm_page_wire(9) -- wire and unwire pages
|
|
The vm_page_wire() function increments the wire count on a page, and removes it from whatever queue it is on. The vm_page_unwire() function releases one of the wirings on the page. When write_count re... |
|
vm_page_zero_fill(9) -- zero fill a page
|
|
The vm_page_zero_fill() function zeros the given vm page by calling the machine dependent pmap_zero_page() routine. vm_page_zero_fill() always returns TRUE. |
|
vm_page_zero_invalid(9) -- manage page clean and dirty bits
|
|
vm_page_bits() calculates the bits representing the DEV_BSIZE range of bytes between base and size. The byte range is expected to be within a single page, and if size is zero, no bits will be set. vm_... |
|
vm_set_page_size(9) -- initialize the system page size
|
|
The vm_set_page_size() function initializes the system page size. If cnt.v_page_size (see ) equals 0, PAGE_SIZE is used; otherwise, the value stored in cnt.v_page_size is used. If cnt.v... |
|
vnode(9) -- internal representation of a file or directory
|
|
The vnode is the focus of all file activity in UNIX. A vnode is described by struct vnode. There is a unique vnode allocated for each active file, each current directory, each mounted-on file, text fi... |
|
vn_isdisk(9) -- checks if a vnode represents a disk
|
|
The vn_isdisk() function checks to see if vp represents a disk. In order for vp to be a disk, it must be a character device, v_rdev must be valid, and the cdevsw entry's flags must have D_DISK set. I... |
|
vn_lock(9) -- serialize access to a vnode
|
|
These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl... |
|
VOP_ACCESS(9) -- check access permissions of a file or Unix domain socket
|
|
This entry point checks the access permissions of the file against the given credentials. Its arguments are: vp the vnode of the file to check mode the type of access required cred the user credential... |
|
VOP_ACLCHECK(9) -- check an access control list for a vnode
|
|
This vnode call may be used to determine the validity of a particular access control list (ACL) for a particular file or directory. Its arguments are: vp the vnode of the file or directory type the ty... |
|
VOP_ADVLOCK(9) -- advisory record locking
|
|
The arguments are: vp the vnode being manipulated id the id token which is changing the lock op the operation to perform (see fcntl(2)) fl description of the lock flags One of more of the following: F... |
|
VOP_ATTRIB(9) -- get and set attributes on a file or directory
|
|
These entry points manipulate various attributes of a file or directory, including file permissions, owner, group, size, access time and modification time. The arguments are: vp the vnode of the file ... |
|
VOP_BWRITE(9) -- write a file system buffer
|
|
The arguments are: vp the vnode of the file being written to bp the buffer to be written |
|
VOP_CLOSE(9) -- open or close a file
|
|
The VOP_OPEN() entry point is called before a file is accessed by a process and the VOP_CLOSE() entry point is called after a file is finished with by the process. The arguments are: vp the vnode of t... |
|
VOP_CREATE(9) -- create a file, socket, fifo, device, directory or symlink
|
|
These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ... |
|
VOP_CREATEVOBJECT(9) -- VM object interaction
|
|
These calls are used to control the association of a VM object with a particular vnode. The arguments specific to these functions are: vp the vnode of the file objpp the VM object being returned, or N... |
|
VOP_DESTROYVOBJECT(9) -- VM object interaction
|
|
These calls are used to control the association of a VM object with a particular vnode. The arguments specific to these functions are: vp the vnode of the file objpp the VM object being returned, or N... |
|
VOP_FSYNC(9) -- flush file system buffers for a file
|
|
This call flushes any dirty file system buffers for the file. It is used to implement the sync(2) and fsync(2) system calls. Its arguments are: vp the vnode of the file cred the caller's credentials ... |
|
VOP_GETACL(9) -- retrieve access control list for a vnode
|
|
This vnode call may be used to retrieve the access control list (ACL) from a file or directory. Its arguments are: vp the vnode of the file or directory type the type of ACL to retrieve aclp a pointer... |
|
VOP_GETATTR(9) -- get and set attributes on a file or directory
|
|
These entry points manipulate various attributes of a file or directory, including file permissions, owner, group, size, access time and modification time. The arguments are: vp the vnode of the file ... |
|
VOP_GETEXTATTR(9) -- retrieve named extended attribute from a vnode
|
|
This vnode call may be used to retrieve a specific named extended attribute from a file or directory. Its arguments are: vp the vnode of the file or directory attrnamespace integer constant indicating... |
|
VOP_GETPAGES(9) -- read or write VM pages from a file
|
|
The VOP_GETPAGES() method is called to read in pages of virtual memory which are backed by ordinary files. If other adjacent pages are backed by adjacent regions of the same file, VOP_GETPAGES() is re... |
|
VOP_GETVOBJECT(9) -- VM object interaction
|
|
These calls are used to control the association of a VM object with a particular vnode. The arguments specific to these functions are: vp the vnode of the file objpp the VM object being returned, or N... |
|
VOP_INACTIVE(9) -- reclaim file system resources for a vnode
|
|
The arguments are: vp the vnode being reclaimed VOP_INACTIVE() is called when the kernel is no longer using the vnode. This may be because the reference count reaches zero or it may be that the file s... |
|
VOP_IOCTL(9) -- device specific control
|
|
Manipulate a file in device dependent ways. Its arguments are: vp the vnode of the file (normally representing a device) command the device specific operation to perform cnp extra data for the specifi... |
|
VOP_ISLOCKED(9) -- serialize access to a vnode
|
|
These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl... |
|
VOP_LEASE(9) -- validate a vnode for a particular set of credentials and operation type
|
|
This entry point is currently not implemented. The idea is to validate a vnode for a particular set of user credentials and operation type. The two operation types supported are LEASE_READ and LEASE_W... |
|
VOP_LINK(9) -- create a new name for a file
|
|
This links a new name in the specified directory to an existing file. Its arguments are: dvp the vnode of the directory vp the vnode of the file to be linked cnp pathname information about the file Th... |
|
VOP_LISTEXTATTR(9) -- retrieve a list of named extended attribute from a vnode
|
|
This vnode call may be used to retrieve a list of named extended attributes from a specified namespace on a file or directory. Its arguments are: vp the vnode of the file or directory attrnamespace in... |
|
VOP_LOCK(9) -- serialize access to a vnode
|
|
These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl... |
|
VOP_LOOKUP(9) -- lookup a component of a pathname
|
|
This entry point looks up a single pathname component in a given directory. Its arguments are: dvp the locked vnode of the directory to search vpp the address of a variable where the resulting locked ... |
|
VOP_MKDIR(9) -- create a file, socket, fifo, device, directory or symlink
|
|
These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ... |
|
VOP_MKNOD(9) -- create a file, socket, fifo, device, directory or symlink
|
|
These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ... |
|
VOP_OPEN(9) -- open or close a file
|
|
The VOP_OPEN() entry point is called before a file is accessed by a process and the VOP_CLOSE() entry point is called after a file is finished with by the process. The arguments are: vp the vnode of t... |
|
VOP_OPENCLOSE(9) -- open or close a file
|
|
The VOP_OPEN() entry point is called before a file is accessed by a process and the VOP_CLOSE() entry point is called after a file is finished with by the process. The arguments are: vp the vnode of t... |
|
VOP_PATHCONF(9) -- return POSIX pathconf information
|
|
The arguments are: vp the vnode to get information about name the type of information to return retval the place to return the information The value of name specifies what should be returned: _PC_LINK... |
|
VOP_PRINT(9) -- print debugging information
|
|
The arguments are: vp the vnode to print |
|
VOP_PUTPAGES(9) -- read or write VM pages from a file
|
|
The VOP_GETPAGES() method is called to read in pages of virtual memory which are backed by ordinary files. If other adjacent pages are backed by adjacent regions of the same file, VOP_GETPAGES() is re... |
|
VOP_RDWR(9) -- read or write a file
|
|
These entry points read or write the contents of a file The arguments are: vp the vnode of the file uio the location of the data to be read or written ioflag various flags cnp the credentials of the c... |
|
VOP_READ(9) -- read or write a file
|
|
These entry points read or write the contents of a file The arguments are: vp the vnode of the file uio the location of the data to be read or written ioflag various flags cnp the credentials of the c... |
|
VOP_READDIR(9) -- read contents of a directory
|
|
Read directory entries. vp the vnode of the directory uio where to read the directory contents cred the caller's credentials eofflag return end of file status (NULL if not wanted) ncookies number of ... |
|
VOP_READLINK(9) -- read the target of a symbolic link
|
|
This reads the target pathname of a symbolic link vp the vnode of the symlink uio the location of the data to be read or written cred the credentials of the caller |
|
VOP_REALLOCBLKS(9) -- rearrange blocks in a file to be contiguous
|
|
The arguments are: vp the file to manipulate buflist a list of buffers to rearrange This seems to be part of a work in progress. |
|
VOP_RECLAIM(9) -- reclaim file system resources for a vnode
|
|
The arguments are: vp the vnode being reclaimed VOP_INACTIVE() is called when the kernel is no longer using the vnode. This may be because the reference count reaches zero or it may be that the file s... |
|
VOP_REMOVE(9) -- remove a file or directory
|
|
These entry points remove files and directories respectively. The arguments are: dvp the vnode of the directory vp the vnode of the file to be removed cnp pathname information about the file |
|
VOP_RENAME(9) -- rename a file
|
|
This renames a file and possibly changes its parent directory. If the destination object exists, it will be removed first. Its arguments are: fdvp the vnode of the old parent directory fvp the vnode o... |
|
VOP_REVOKE(9) -- revoke access to a device and its aliases
|
|
VOP_REVOKE() will administratively revoke access to the device specified by vp, as well as any aliases created via make_dev_alias(9). Further file operations on any of these devices by processes which... |
|
VOP_RMDIR(9) -- remove a file or directory
|
|
These entry points remove files and directories respectively. The arguments are: dvp the vnode of the directory vp the vnode of the file to be removed cnp pathname information about the file |
|
VOP_SETACL(9) -- set the access control list for a vnode
|
|
This vnode call may be used to set the access control list (ACL) for a file or directory. Its arguments are: vp the vnode of the file or directory type the type of ACL to set aclp a pointer to an ACL ... |
|
VOP_SETATTR(9) -- get and set attributes on a file or directory
|
|
These entry points manipulate various attributes of a file or directory, including file permissions, owner, group, size, access time and modification time. The arguments are: vp the vnode of the file ... |
|
VOP_SETEXTATTR(9) -- set named extended attribute for a vnode
|
|
This vnode call may be used to set specific named extended attribute for a file or directory. Its arguments are: vp the vnode of the file or directory attrnamespace integer constant indicating which e... |
|
VOP_STRATEGY(9) -- read or write a file system buffer
|
|
The arguments are: vp the vnode that the buffer is for bp the buffer to be read or written This call either reads or writes data from a file, depending on the value of bp->b_io.bio_cmd. The call may b... |
|
VOP_SYMLINK(9) -- create a file, socket, fifo, device, directory or symlink
|
|
These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ... |
|
VOP_UNLOCK(9) -- serialize access to a vnode
|
|
These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl... |
|
VOP_WRITE(9) -- read or write a file
|
|
These entry points read or write the contents of a file The arguments are: vp the vnode of the file uio the location of the data to be read or written ioflag various flags cnp the credentials of the c... |
|
vput(9) -- decrement the use count for a vnode and unlock it
|
|
Decrement the v_usecount field of a vnode and unlock the vnode. vp the vnode to decrement This operation is functionally equivalent to calling VOP_UNLOCK(9) followed by vrele(9). |
|
vref(9) -- increment the use count for a vnode
|
|
Increment the v_usecount field of a vnode. vp the vnode to increment 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... |
|
VREF(9) -- increment the use count for a vnode
|
|
Increment the v_usecount field of a vnode. vp the vnode to increment 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... |
|
vrele(9) -- decrement the use count for a vnode
|
|
Decrement the v_usecount field of a vnode. vp the vnode to decrement Any code in the system which is using a vnode should call vrele() when it is finished with the vnode. If the v_usecount field of th... |
|
vslock(9) -- lock/unlock user space addresses in memory
|
|
The vslock() and vsunlock() functions respectively lock and unlock a range of addresses belonging to the currently running process into memory. The actual amount of memory locked is a multiple of the ... |
|
vsunlock(9) -- lock/unlock user space addresses in memory
|
|
The vslock() and vsunlock() functions respectively lock and unlock a range of addresses belonging to the currently running process into memory. The actual amount of memory locked is a multiple of the ... |
|
wakeup(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
wakeup_one(9) -- wait for events
|
|
The functions tsleep() and wakeup() handle event-based process blocking. If a process must wait for an external event, it is put on sleep by tsleep(). The parameter ident is an arbitrary address that ... |
|
zero_copy(9) -- 0zero_copy, zero_copy_sockets
|
|
The FreeBSD kernel includes a facility for eliminating data copies on socket reads and writes. This code is collectively known as the zero copy sockets code, because during normal network I/O, data wi... |
|
zero_copy_sockets(9) -- 0zero_copy, zero_copy_sockets
|
|
The FreeBSD kernel includes a facility for eliminating data copies on socket reads and writes. This code is collectively known as the zero copy sockets code, because during normal network I/O, data wi... |
|
zone(9) -- zone allocator
|
|
The zone allocator provides an efficient interface for managing dynamically-sized collections of items of similar size. The zone allocator can work with preallocated zones as well as with runtime-allo... |
|
zpfind(9) -- locate a process by number
|
|
pfind() takes a pid as its argument and returns a pointer to the proc structure whose PID is specified in the argument only if the pid is on the allproc list. zpfind() takes a pid as its argument. If ... |
