Re: [(RT RFC) PATCH v2 8/9] adjust pi_lock usage in wakeup

2008-02-25 Thread Pavel Machek
On Mon 2008-02-25 11:01:18, Gregory Haskins wrote: > From: Peter W.Morreale <[EMAIL PROTECTED]> > > In wakeup_next_waiter(), we take the pi_lock, and then find out whether > we have another waiter to add to the pending owner. We can reduce > contention on the pi_lock for the pending owner if we

[(RT RFC) PATCH v2 8/9] adjust pi_lock usage in wakeup

2008-02-25 Thread Gregory Haskins
From: Peter W.Morreale <[EMAIL PROTECTED]> In wakeup_next_waiter(), we take the pi_lock, and then find out whether we have another waiter to add to the pending owner. We can reduce contention on the pi_lock for the pending owner if we first obtain the pointer to the next waiter outside of the

[(RT RFC) PATCH v2 8/9] adjust pi_lock usage in wakeup

2008-02-25 Thread Gregory Haskins
From: Peter W.Morreale [EMAIL PROTECTED] In wakeup_next_waiter(), we take the pi_lock, and then find out whether we have another waiter to add to the pending owner. We can reduce contention on the pi_lock for the pending owner if we first obtain the pointer to the next waiter outside of the

Re: [(RT RFC) PATCH v2 8/9] adjust pi_lock usage in wakeup

2008-02-25 Thread Pavel Machek
On Mon 2008-02-25 11:01:18, Gregory Haskins wrote: From: Peter W.Morreale [EMAIL PROTECTED] In wakeup_next_waiter(), we take the pi_lock, and then find out whether we have another waiter to add to the pending owner. We can reduce contention on the pi_lock for the pending owner if we first