Re: [PATCHv3 1/9] sched: Add static_key for asymmetric cpu capacity optimizations

[Dietmar Eggemann]

On 06/22/2018 04:36 PM, Morten Rasmussen wrote:
> On Fri, Jun 22, 2018 at 09:22:22AM +0100, Quentin Perret wrote:
> > Hi Morten,
> >
> > On Wednesday 20 Jun 2018 at 10:05:41 (+0100), Morten Rasmussen wrote:
> > > +static void update_asym_cpucapacity(int cpu)
> > > +{
> > > +	int enable = false;
> > > +
> > > +	rcu_read_lock();
> > > +	if (lowest_flag_domain(cpu, SD_ASYM_CPUCAPACITY))
> > > +		enable = true;
> > > +	rcu_read_unlock();
> > > +
> > > +	if (enable) {
> > > +		/* This expects to be hotplug-safe */
> > > +		static_branch_enable_cpuslocked(&sched_asym_cpucapacity);
> > > +	}
> > > +}
> >
> > What would happen if you hotplugged an entire cluster ? You'd loose the
> > SD_ASYM_CPUCAPACITY flag but keep the static key is that right ? Should
> > we care ?
>
> I don't think we should care. The static key enables additional checks
> and tweaks but AFAICT none of them requires the SD_ASYM_CPUCAPACITY to
> be set and they should all be have no effect if that is the case. I
> added the static key just avoid the overhead on systems where they would
> have no effect. At least that is intention, I could course have broken
> things by mistake.

I tent to agree for misfit but it would be easy to just add an 
static_branch_disable_cpuslocked() into the else path of if(enable).

> > And also, Peter mentioned an issue with the EAS patches with multiple
> > root_domains. Does that apply here as well ? What if you had a
> > configuration with big and little CPUs in different root_domains for ex?
> >
> > Should we disable the static key in the above cases ?
>
> Exclusive cpusets are more tricky as the flags will be the same for
> sched_domains at the same level. So we can't set the flag correctly if
> someone configures the exclusive cpusets such that you have one
> root_domain spanning big and a subset of little, and one spanning the
> remaining little cpus if all topology levels are preserved. If we
> imagine a three cluster system where 0-3 and 4-7 little clusters, and
> 8-11 is a big cluster with cpusets configured as 0-5 and 6-11. The first
> set should _not_ have SD_ASYM_CPUCAPACITY set, while the second should.
>
> I'm tempted to say we shouldn't care in this situation. Setting the
> flags correctly in the three cluster example would require knowledge
> about the cpuset configuration which we don't have in the arch code so
> SD_ASYM_CPUCAPACITY flag detection would have be done by the
> sched_domain build code. However, not setting the flag according to the
> actual members of the exclusive cpuset means that homogeneous
> sched_domains might have SD_ASYM_CPUCAPACITY set enabling potentially
> wrong scheduling decisions.

We could easily pass the CPU as an argument to all these 
sched_domain_flags_f functions.

-typedef int (*sched_domain_flags_f)(void);
+typedef int (*sched_domain_flags_f)(int cpu);

In this case, the arch specific flag functions on a sched domain (sd) 
level could use the corresponding sched_domain_mask_f function to 
iterate over the span of the sd seen by CPU instead of all online cpus.

The overall question is ... do we need sd setups which are asymmetric 
(different topology flags for sd hierarchies seen by different CPUs) and 
does the scheduler cope with this?

We have seen 3 cluster systems like the MediaTek X20 (2 A72, 4 A53 (max 
1.85Ghz), 4 A53 (max 1.4Ghz)) but this would rather be a big-little-tiny 
system due to the max CPU frequency differences between the A53's.

We could also say that systems with 2 clusters with the same uArch and 
same max CPU frequency and additional clusters are insane, like we e.g. 
do with the Energy Model and CPUs with different uArch within a 
frequency domain?

> We can actually end up with this problem just by hotplugging too. If you
> unplug the entire big cluster in the three cluster example above, you
> preserve DIE level which would have SD_ASYM_CPUCAPACITY set even though
> we only have little cpus left.
>
> As I see it, we have two choices: 1) Set the flags correctly for
> exclusive cpusets which means some additional "fun" in the sched_domain
> hierarchy set up, or 2) ignore it and make sure that setting

I assume you refer to this cpu parameter for sched_domain_flags_f under 1).

> SD_ASYM_CPUCAPACITY on homogeneous sched_domains works fairly okay. The
> latter seems easier.
>
> Morten