From: Tim Chen <tim.c.chen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ricardo Neri <ricardo.neri@intel.com>,
"Ravi V . Shankar" <ravi.v.shankar@intel.com>,
Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Len Brown <len.brown@intel.com>, Mel Gorman <mgorman@suse.de>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Shrikanth Hegde <sshegde@linux.vnet.ibm.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
naveen.n.rao@linux.vnet.ibm.com,
Yicong Yang <yangyicong@hisilicon.com>,
Barry Song <v-songbaohua@oppo.com>, Chen Yu <yu.c.chen@intel.com>,
Hillf Danton <hdanton@sina.com>
Subject: Re: [Patch v2 2/6] sched/topology: Record number of cores in sched group
Date: Mon, 12 Jun 2023 13:16:52 -0700 [thread overview]
Message-ID: <f493a770e15a81aaad2e13d8afe1daf939b8267a.camel@linux.intel.com> (raw)
In-Reply-To: <20230612112945.GK4253@hirez.programming.kicks-ass.net>
On Mon, 2023-06-12 at 13:29 +0200, Peter Zijlstra wrote:
> On Thu, Jun 08, 2023 at 03:32:28PM -0700, Tim Chen wrote:
> >
> > sg->group_weight = cpumask_weight(sched_group_span(sg));
> >
> > + cpumask_copy(mask, sched_group_span(sg));
> > + for_each_cpu(cpu, mask) {
> > + cores++;
> > + cpumask_andnot(mask, mask, cpu_smt_mask(cpu));
> > + }
> > + sg->cores = cores;
> > +
> > if (!(sd->flags & SD_ASYM_PACKING))
> > goto next;
>
> Just a note; not sure we want or can do anything about this, but
> consider someone doing partitions like:
>
> [0,1] [2,3] [3,6]
> [------] [------]
>
> That is, 3 SMT cores, and 2 partitions splitting an SMT core in two.
>
> Then the domain trees will see either 2 or 3 but not the fully core.
>
> I'm perfectly fine with saying: don't do that then.
I also can't see a reason to split SMT between two domains.
Tim
next prev parent reply other threads:[~2023-06-12 20:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 22:32 [Patch v2 0/6] Enable Cluster Scheduling for x86 Hybrid CPUs Tim Chen
2023-06-08 22:32 ` [Patch v2 1/6] sched/fair: Determine active load balance for SMT sched groups Tim Chen
2023-06-12 11:13 ` Peter Zijlstra
2023-06-12 20:12 ` Tim Chen
2023-06-12 20:14 ` Peter Zijlstra
2023-06-12 11:16 ` Peter Zijlstra
2023-06-12 20:12 ` Tim Chen
2023-06-08 22:32 ` [Patch v2 2/6] sched/topology: Record number of cores in sched group Tim Chen
2023-06-12 11:29 ` Peter Zijlstra
2023-06-12 20:16 ` Tim Chen [this message]
2023-06-08 22:32 ` [Patch v2 3/6] sched/fair: Implement prefer sibling imbalance calculation between asymmetric groups Tim Chen
2023-06-12 12:05 ` Peter Zijlstra
2023-06-13 17:46 ` Tim Chen
2023-06-15 11:07 ` Peter Zijlstra
2023-06-15 17:01 ` Tim Chen
2023-06-08 22:32 ` [Patch v2 4/6] sched/fair: Consider the idle state of the whole core for load balance Tim Chen
2023-06-08 22:32 ` [Patch v2 5/6] sched/x86: Add cluster topology to hybrid CPU Tim Chen
2023-06-08 22:32 ` [Patch v2 6/6] sched/debug: Dump domains' sched group flags Tim Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f493a770e15a81aaad2e13d8afe1daf939b8267a.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hdanton@sina.com \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sshegde@linux.vnet.ibm.com \
--cc=v-songbaohua@oppo.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yu.c.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox