Lines Matching refs:function

11    if executing the function reaches a reschedule point
13    if executing the function can cause the invoking thread to sleep
15    if a parameter to the function can prevent the invoking thread from
18    if the function can be safely called and will have its specified
21    if the function can be safely called before the kernel has been fully
25    if the function may return before the operation it initializes is
26    complete (i.e. function return and operation completion are
30    function
40 The reschedule attribute is used on a function that can reach a
46 The significance of this attribute is that when a rescheduling function
54 interrupts, any thread may be suspended in any function.
69 The sleep attribute is used on a function that can cause the invoking
81 This attribute does not imply the function will sleep unconditionally,
98 The no-wait attribute is used on a function that is also **sleep** to
99 indicate that a parameter to the function can force an execution path
105 The paradigmatic case of a no-wait function is a function that takes a
107 this special timeout value are to execute the function's operation as
115 A function with a no-wait path does not imply that taking that path
116 guarantees the function is synchronous.
126 The isr-ok attribute is used on a function to indicate that it works
132 Any function that is not **sleep** is inherently **isr-ok**.  Functions
138 function will return a specific error (generally ``-EWOULDBLOCK``).
140 Note that a function that is **no-wait** is safe to call from interrupt
149 The pre-kernel-ok attribute is used on a function to indicate that it
156 This attribute is similar to **isr-ok** in function, but is intended for
161 Generally a function that is **pre-kernel-ok** checks
171 A function is **async** (i.e. asynchronous) if it may return before the
172 operation it initiates has completed.  An asynchronous function will
176 A function that is not asynchronous is synchronous, i.e. the operation
177 will always be complete when the function returns.  As most functions
189 If a function is both **no-wait** and **async** then selecting the
190 no-wait path only guarantees that the function will not sleep.  It does
191 not affect whether the operation will be completed before the function
200 indicates that the function cannot be invoked from user mode.