Re: [PATCH 2/4] sched/deadline: Improve admission control for asymmetric CPU capacities

Dietmar Eggemann
2020-04-17T14:55:41Z

On 17.04.20 14:19, Juri Lelli wrote:
> On 09/04/20 19:29, Dietmar Eggemann wrote:

[...]

>> Maybe we can do a hybrid. We have rd->span and rd->sum_cpu_capacity and
>> with the help of an extra per-cpu cpumask we could just
>
> Hummm, I like the idea, but
>
>> DEFINE_PER_CPU(cpumask_var_t, dl_bw_mask);
>>
>> dl_bw_cpus(int i) {
>
> This works if calls are always local to the rd we are interested into
> (argument 'i' isn't used). Are we always doing that?

I thought so. The existing dl_bw_cpus(int i) implementation already
assumes this by using:

struct root_domain *rd = cpu_rq(i)->rd;

...

for_each_cpu_and(i, rd->span, cpu_active_mask)

Or did you refer to something else here?

And the patch would not introduce new places in which we call
dl_bw_cpus(). It will just replace some with a dl_bw_capacity() call.

>> struct cpumask *cpus = this_cpu_cpumask_var_ptr(dl_bw_mask);
>> ...
>> cpumask_and(cpus, rd->span, cpu_active_mask);
>>
>> return cpumask_weight(cpus);
>> }
>>
>> and
>>
>> dl_bw_capacity(int i) {
>>
>> struct cpumask *cpus = this_cpu_cpumask_var_ptr(dl_bw_mask);
>> ...
>> cpumask_and(cpus, rd->span, cpu_active_mask);
>> if (cpumask_equal(cpus, rd->span))
>> return rd->sum_cpu_capacity;
>
> What if capacities change between invocations (with the same span)?
> Can that happen?

The CPU capacity should only change during initial bring-up. On
asymmetric CPU capacity systems we have to re-create the Sched Domain
(SD) topology after CPUfreq becomes available.

After the initial build and this first rebuild of the SD topology, the
CPU capacity should be stable.

Everything which might follow afterwards (starting EAS, exclusive
cpusets or CPU hp) will not change the CPU capacity.

Obviously, if you defer loading CPUfreq driver after you started DL
scheduling you can break things. But this is not considered a valid
environment here. …