On Thu, May 24, 2018 at 05:29:36PM +0200, Juri Lelli wrote:
> When scheduler debug is enabled, building scheduling domains outputs
> information about how the domains are laid out and to which root domain
> each CPU (or sets of CPUs) belongs, e.g.:
>
> CPU0 attaching sched-domain(s):
> domain-0
On 25/05/18 13:35, Dietmar Eggemann wrote:
[...]
>
> Looks good to me. Probably especially helpful when setting up exclusive
> cpusets.
>
> Juno with big and little exclusive cpuset:
>
> ...
> [ 124.231333] CPU1 attaching sched-domain(s):
> [ 124.235482] domain-0: span=1-2 level=MC
> [ 124
On 05/24/2018 05:29 PM, Juri Lelli wrote:
When scheduler debug is enabled, building scheduling domains outputs
information about how the domains are laid out and to which root domain
each CPU (or sets of CPUs) belongs, e.g.:
CPU0 attaching sched-domain(s):
domain-0: span=0-5 level=MC
gr
When scheduler debug is enabled, building scheduling domains outputs
information about how the domains are laid out and to which root domain
each CPU (or sets of CPUs) belongs, e.g.:
CPU0 attaching sched-domain(s):
domain-0: span=0-5 level=MC
groups: 0:{ span=0 }, 1:{ span=1 }, 2:{ span=2 },
4 matches
Mail list logo
