Srikar Dronamraju writes:
> * Michael Ellerman [2021-09-23 21:17:25]:
>
>> Srikar Dronamraju writes:
>> > * Michael Ellerman [2021-08-26 23:36:53]:
>> >
>> >> Srikar Dronamraju writes:
>> >> > Scheduler expects unique number of node distances to be available at
>> >> > boot.
>> ...
>> >
>> >>
* Michael Ellerman [2021-09-23 21:17:25]:
> Srikar Dronamraju writes:
> > * Michael Ellerman [2021-08-26 23:36:53]:
> >
> >> Srikar Dronamraju writes:
> >> > Scheduler expects unique number of node distances to be available at
> >> > boot.
> ...
> >
> >> > Fake the offline node's distance_look
Srikar Dronamraju writes:
> * Michael Ellerman [2021-08-26 23:36:53]:
>
>> Srikar Dronamraju writes:
>> > Scheduler expects unique number of node distances to be available at
>> > boot.
...
>
>> > Fake the offline node's distance_lookup_table entries so that all
>> > possible node distances are
* Michael Ellerman [2021-08-26 23:36:53]:
> Srikar Dronamraju writes:
> > Scheduler expects unique number of node distances to be available at
> > boot.
>
> I think it needs "the number of unique node distances" ?
>
> > It uses node distance to calculate this unique node distances.
>
> It ite
Srikar Dronamraju writes:
> Scheduler expects unique number of node distances to be available at
> boot.
I think it needs "the number of unique node distances" ?
> It uses node distance to calculate this unique node distances.
It iterates over all pairs of nodes and records node_distance() for
Scheduler expects unique number of node distances to be available at
boot. It uses node distance to calculate this unique node distances.
On POWER, node distances for offline nodes is not available. However,
POWER already knows unique possible node distances. Fake the offline
node's distance_lookup
