|
|
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... |
