Lines Matching refs:as

19 efficient code as both threads can continue until the result is actually
60 Good naming (as always) helps code readability.
77 most likely a bug as it re-initializes the queue to an empty queue and
95 _interruptible/_killable variants is not advisable as they will require
120 immediately as all dependencies are satisfied if not it will block until
132 The default behavior is to wait without a timeout and to mark the task as
134 in process context (as they can sleep) but not in atomic context,
167 The task is marked as TASK_UNINTERRUPTIBLE and will wait at most 'timeout'
177 This function passes a timeout in jiffies and marks the task as
182 Further variants include _killable which uses TASK_KILLABLE as the
184 else 0 if completion was achieved.  There is a _timeout variant as well:
190 The _io variants wait_for_completion_io() behave the same as the non-_io
191 variants, except for accounting waiting time as waiting on IO, which has
212 The signaling will work as expected even if completions are signaled before
227 Signaling completion from hard-irq context is fine as it will appropriately