Re: [RFC PATCH v3 08/16] sched: Rework pick_next_task() slow-path

2019-08-26 Thread mark gross
On Wed, May 29, 2019 at 08:36:44PM +, Vineeth Remanan Pillai wrote: > From: Peter Zijlstra > > Avoid the RETRY_TASK case in the pick_next_task() slow path. > > By doing the put_prev_task() early, we get the rt/deadline pull done, > and by testing rq->nr_running we know if we need newidle_bal

[RFC PATCH v3 08/16] sched: Rework pick_next_task() slow-path

2019-05-29 Thread Vineeth Remanan Pillai
From: Peter Zijlstra Avoid the RETRY_TASK case in the pick_next_task() slow path. By doing the put_prev_task() early, we get the rt/deadline pull done, and by testing rq->nr_running we know if we need newidle_balance(). This then gives a stable state to pick a task from. Since the fast-path is