Lines Matching +full:channel +full:- +full:use

1 .\" Copyright (c) 2000-2004 John H. Baldwin <jhb@FreeBSD.org>
3 .\" Redistribution and use in source and binary forms, with or without
17 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
20 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
92 Each queue is associated with a specific wait channel when it is active,
93 and only one queue may be associated with a wait channel at any given point
95 The implementation of each wait channel splits its sleepqueue into 2 sub-queues
98 wait channel.
99 Threads that are not blocked on a wait channel have an associated inactive
101 When a thread blocks on a wait channel it donates its inactive sleep queue
102 to the wait channel.
104 the wait channel that it was blocked on gives it an inactive sleep queue for
105 later use.
128 function locks the sleep queue chain associated with wait channel
134 channel associated with
156 wait channel
180 parameter specifies the sub-queue, in which the contending thread will be
185 .Bl -tag -width ".Dv SLEEPQ_CONDVAR" -compact
201 .Bl -tag -width ".Dv SLEEPQ_INTERRUPTIBLE" -compact
205 .Bl -tag -width ".Dv SLEEPQ_STOP_ON_BDRY" -compact
251 function is used for non-interruptible sleeps that do not have a timeout.
254 function is used for non-interruptible sleeps that have had a timeout set via
264 argument to all of the wait functions is the wait channel being slept
276 the wait functions return a non-zero value if the thread was awakened due to
291 function awakens the highest priority thread sleeping on a wait channel
294 awakens all of the threads sleeping on a wait channel.
297 argument specifics which wait channel to awaken.
304 by the threads sleeping on the wait channel.
307 argument does not equal \-1,
318 argument specifies the sub-queue, from which threads need to be woken up.
328 channel via the
335 argument specifies the wait channel to awaken it from.
338 is not blocked on the wait channel
341 even if the thread is asleep on a different wait channel.
344 One possible use is waking up a specific thread from a widely shared sleep
345 channel.
381 Almost all other code in the kernel should use one of those interfaces rather