Re: [RFC PATCH v3 07/16] sched: Allow put_prev_task() to drop rq->lock

On Wed, May 29, 2019 at 08:36:43PM +, Vineeth Remanan Pillai wrote: > From: Peter Zijlstra > > Currently the pick_next_task() loop is convoluted and ugly because of > how it can drop the rq->lock and needs to restart the picking. > > For the RT/Deadline classes, it is put_prev_task() where w

[RFC PATCH v3 07/16] sched: Allow put_prev_task() to drop rq->lock

From: Peter Zijlstra Currently the pick_next_task() loop is convoluted and ugly because of how it can drop the rq->lock and needs to restart the picking. For the RT/Deadline classes, it is put_prev_task() where we do balancing, and we could do this before the picking loop. Make this possible. S