.Vt struct kevent is taken to be a file descriptor. In this case, the
.Vt knote passed into f_attach will have the kn_fp member initialized to the
.Vt struct file * that represents the file descriptor.
function will be called when attaching a
.Vt knote to the object. The method should call knlist_add to add the
.Vt knote to the list that was initialized with knlist_init. The call to knlist_add is only necessary if the object can have multiple
.Vt knotes associated with it. If there is no
.Vt knlist to call knlist_add with, the function f_attach must clear the KN_DETACHED bit of kn_status in the
.Vt knote . The function shall return 0 on success, or appropriate error for the failure, such as when the object is being destroyed, or does not exist. During f_attach, it is valid to change the kn_fops pointer to a different pointer. This will change the f_event and f_detach functions called when processing the
.Vt knote .
function will be called to detach the
.Vt knote if the
.Vt knote has not already been detached by a call to knlist_remove, knlist_remove_inevent or knlist_delete. The list lock will not be held when this function is called.
function will be called to update the status of the
.Vt knote . If the function returns 0, it will be assumed that the object is not ready (or no longer ready) to be woken up. The hint argument will be 0 when scanning
.Vt knotes to see which are triggered. Otherwise, the hint argument will be the value passed to either KNOTE_LOCKED or KNOTE_UNLOCKED. The kn_data value should be updated as necessary to reflect the current value, such as number of bytes available for reading, or buffer space available for writing. If the note needs to be removed, knlist_remove_inevent must be called. The function knlist_remove_inevent will remove the note from the list, the f_detach function will not be called and the
.Vt knote will not be returned as an event.
be acquired in
If a lock is required in
it must be obtained in the
function of the
will register the
.Vt kevent on the kqueue file descriptor fd. If it is safe to sleep, waitok should be set.
is used to delete all
.Vt knotes associated with fd. Once returned, there will no longer be any
.Vt knotes associated with the fd. The
.Vt knotes removed will never be returned from a kevent(2) call, so if userland uses the
.Vt knote to track resources, they will be leaked. The FILEDESC_LOCK lock must be held over the call to knote_fdclose so that file descriptors cannot be added or removed.
family of functions are for managing
.Vt knotes associated with an object. A
.Vt knlist is not required, but is commonly used. If used, the
.Vt knlist must be initialized with either knlist_init, knlist_init_mtx or knlist_init_rw_reader. The
.Vt knlist structure may be embedded into the object structure. The lock will be held over f_event calls.
For the knlist_init function, if lock is NULL, a shared global lock will be used and the remaining arguments must be NULL. The function pointers kl_lock, kl_unlock and kl_locked will be used to manipulate the argument lock. If any of the function pointers are NULL, a function operating on MTX_DEF style mutex(9) locks will be used instead.
may be used to initialize a
.Vt knlist when lock is a MTX_DEF style mutex(9) lock.
may be used to initialize a
.Vt knlist when lock is a rwlock(9) read lock. Lock is acquired via rw_rlock function.
returns true when there are no
.Vt knotes on the list. The function requires that the lock be held when called.
.Vt knotes from the list. The islocked argument declares if the lock has been acquired. All
.Vt knotes will have EV_ONESHOT set so that the
.Vt knote will be returned and removed durning the next scan. The f_detach function will be called when the
.Vt knote is deleted durning the next scan. This function must not be used when f_isfd is set in
.Vt struct filterops , as the td argument of fdrop will be NULL.
removes and deletes all
.Vt knotes on the list. The function f_detach will not be called, and the
.Vt knote will not be returned on the next scan. Using this function could leak user land resources if a process uses the
.Vt knote to track resources.
functions may sleep.
They also may release the
to wait for other
.Vt knotes to drain.
function is used to destroy a
.Vt knlist . There must be no
.Vt knotes associated with the
.Vt knlist ( knlist_empty returns true) and no more
.Vt knotes may be attached to the object. A
.Vt knlist may be emptied by calling knlist_clear or knlist_delete.
are used to notify
.Vt knotes about events associated with the object. It will iterate over all
.Vt knotes on the list calling the f_event function associated with the
.Vt knote . The macro KNOTE_LOCKED must be used if the lock associated with the knl is held. The function KNOTE_UNLOCKED will acquire the lock before iterating over the list of
.Vt knotes .
The function kqueue_add_filteropts will return zero on success, EINVAL in the case of an invalid filt, or EEXIST if the filter has already been installed.
The function kqueue_del_filteropts will return zero on success, EINVAL in the case of an invalid filt, or EBUSY if the filter is still in use.
The function kqfd_register will return zero on success, EBADF if the file descriptor is not a kqueue, or any of the possible values returned by kevent(2).
This manual page was written by
.An John-Mark Gurney Aq jmg@FreeBSD.org .