On Tue, 19 May 2015, Davidlohr Bueso wrote: > Mark the task for later wakeup after the wait_lock has been released. > This way, once the next task is awoken, it will have a better chance > to of finding the wait_lock free when continuing executing in > __rt_mutex_slowlock() when trying to acquire the rtmutex, calling > try_to_take_rt_mutex(). Upon contended scenarios, other tasks attempting > take the lock may acquire it first, right after the wait_lock is released, > but (a) this can also occur with the current code, as it relies on the > spinlock fairness, and (b) we are dealing with the top-waiter anyway, > so it will always take the lock next. > > Signed-off-by: Davidlohr Bueso <dbu...@suse.de>
Reviewed-by: Thomas Gleixner <t...@linutronix.de> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
