#include <sys/ksynch.h> #include <sys/ddi.h>
void SLEEP_LOCK(sleep_t *lockp, int priority);
The caller will not be interrupted by signals while sleeping inside SLEEP_LOCK.
Drivers may use these values to request a priority appropriate to a given type of device or to request a priority that is high, medium or low relative to other activities within the kernel.
It is also permissible to specify positive or negative offsets from the values defined above. Positive offsets result in more favorable priority. The maximum allowable offset in all cases is 3 (for example, pridisk+3 and pridisk-3 are valid values but pridisk+4 and pridisk-4 are not valid). Offsets can be useful in defining the relative importance of different locks or resources that may be held by a given driver. In general, a higher relative priority should be used when the caller is attempting to acquire a highly contended lock or resource, or when the caller is already holding one or more locks or kernel resources upon entry to SLEEP_LOCK.
The exact semantic of the priority argument is specific to the scheduling class of the caller, and some scheduling classes may choose to ignore the argument for the purposes of assigning a scheduling priority.
Sleep locks are not recursive. A call to SLEEP_LOCK attempting to acquire a lock that is currently held by the calling context will result in deadlock.
``Sleep locks'' in HDK Technical Reference