On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote:
> Priority propagation will already handle things ok.  We drop to pri_native
> after we drop a lock (although if we still hold a contested lock we bump our
> priority to the min(nativepri, highest priority of threads on contested locks
> we hold and drop to nativepri after dropping the last contested lock). 

ok, thanks for the clarification

> However, kthreads should tsleep() with their current priority, not PPAUSE.

"current" meaning pri_level or pri_native ? What if one tries to
tsleep() while holding a lock and so its pri_level is raised ?

In the device polling code i did a tsleep on the "original" pri_level,
but maybe pri_native is good enough.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to