On 30 October 2017 at 17:19, Joel Fernandes wrote:
> Hi Vincent,
>
> On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
> wrote:
>> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>>> find_idlest_group_cpu goes through CPUs of a group previous selected by
>>> find_idlest_group. find_idlest_grou
Hi Vincent,
On Mon, Oct 30, 2017 at 9:00 AM, Vincent Guittot
wrote:
> On 28 October 2017 at 11:59, Joel Fernandes wrote:
>> find_idlest_group_cpu goes through CPUs of a group previous selected by
>> find_idlest_group. find_idlest_group returns NULL if the local group is the
>> selected one and d
On 28 October 2017 at 11:59, Joel Fernandes wrote:
> find_idlest_group_cpu goes through CPUs of a group previous selected by
> find_idlest_group. find_idlest_group returns NULL if the local group is the
> selected one and doesn't execute find_idlest_group_cpu if the group to which
> 'cpu' belongs
On Sat, Oct 28 2017 at 09:59, Joel Fernandes wrote:
> find_idlest_group_cpu goes through CPUs of a group previous selected by
> find_idlest_group. find_idlest_group returns NULL if the local group is the
> selected one and doesn't execute find_idlest_group_cpu if the group to which
> 'cpu' belongs
find_idlest_group_cpu goes through CPUs of a group previous selected by
find_idlest_group. find_idlest_group returns NULL if the local group is the
selected one and doesn't execute find_idlest_group_cpu if the group to which
'cpu' belongs to is chosen. So we're always guaranteed to call
find_idlest
5 matches
Mail list logo