Re: [PATCH v3 02/12] sched: remove a wake_affine condition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/30/2014 12:05 PM, Vincent Guittot wrote: > I have tried to understand the meaning of the condition : > (this_load <= load && this_load + target_load(prev_cpu, idx) <= > tl_per_task) but i failed to find a use case that can take > advantage of

Re: [PATCH v3 02/12] sched: remove a wake_affine condition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/30/2014 12:05 PM, Vincent Guittot wrote: I have tried to understand the meaning of the condition : (this_load = load this_load + target_load(prev_cpu, idx) = tl_per_task) but i failed to find a use case that can take advantage of it and i

[PATCH v3 02/12] sched: remove a wake_affine condition

I have tried to understand the meaning of the condition : (this_load <= load && this_load + target_load(prev_cpu, idx) <= tl_per_task) but i failed to find a use case that can take advantage of it and i haven't found clear description in the previous commits' log. Futhermore, the comment of the

[PATCH v3 02/12] sched: remove a wake_affine condition

I have tried to understand the meaning of the condition : (this_load = load this_load + target_load(prev_cpu, idx) = tl_per_task) but i failed to find a use case that can take advantage of it and i haven't found clear description in the previous commits' log. Futhermore, the comment of the