linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
	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: [Patch v2 0/6] Enable Cluster Scheduling for x86 Hybrid CPUs
Date: Thu,  8 Jun 2023 15:32:26 -0700	[thread overview]
Message-ID: <cover.1686263351.git.tim.c.chen@linux.intel.com> (raw)

This is the second version of patches to fix issues to allow cluster
scheduling on x86 hybrid CPUs.  It addresses concerns by
reviewers in the first version:
https://lore.kernel.org/lkml/CAKfTPtD1W6vJQBsNKEt_4tn2EeAs=73CeH4LoCwENrh2JUDwnQ@mail.gmail.com/T/

The review comments were greatly appreciated.

Changes from v1:
1. Peter pointed out that the number of CPUs in a cluster could
also be modified by bringing CPU on or offline. Balance between the
sibling clusters should not just take into consideration of whether a
cluster has SMT CPUs or pure core CPUs.  In this version, I take the
approach to balance tasks between the clusters such that the
running_tasks/num_cores between the clusters are similar.  This would
accommodate balance between SMT clusters and non-SMT clusters,
or between the same clusters with different number of cores.

2. Vincent pointed out that special case logic in the general path
for detection of fully busy SMT can be simplified.  Fully busy SMT could
be detected during statistics gathering and will make the code cleaner
by detecting such cases there.  This version of the patch series makes
this change.

3. Suggestions by Chen Yu and Hillf Danton to improve commit logs. 

4. Patch by Peter to dump domain sched groups' flags and
include suggestions by Peter to simplify code.

The performance of this version is similar to the previous version for
other benchmarks, though kbuild is about a couple percents worse.
Experiments were done on Alder Lake with 6 P-cores and 8 E-cores,
organized in two clusters of 4 E-core each.

Single Threaded	6.3-rc5 		with cluster 	   Improvement
Benchmark				scheduling	   in Performance
		(run-run deviation) 	(run-run deviation)
-------------------------------------------------------------------------------------------
tjbench		(+/- 0.08%)		(+/- 0.51%)	   -0.34%
PhPbench	(+/- 0.31%)		(+/- 2.48%)	   -0.99%
flac		(+/- 0.58%)		(+/- 0.86%)	   +0.61%
pybench		(+/- 3.16%)		(+/- 3.36%)	   +1.36%


Multi Threaded	6.3-rc5 		with cluster 	   Improvement
Benchmark				scheduling	   in Performance
(-#threads)	(run-run deviation) 	(run-run deviation)
-------------------------------------------------------------------------------------------
Kbuild-8	(+/- 2.90%)		(+/- 0.24%)	   -1.63%
Kbuild-10	(+/- 3.08%)		(+/- 0.47%)	   -2.06%
Kbuild-12	(+/- 3.28%)		(+/- 0.28%)	   -1.38%
Tensor Lite-8	(+/- 4.84%)		(+/- 3.21%)	   -0.57%
Tensor Lite-10	(+/- 0.87%)		(+/- 1.21%)	   -1.00%
Tensor Lite-12	(+/- 1.37%)		(+/- 0.43%)	   -0.05%

Tim Chen

Ricardo Neri (1):
  sched/fair: Consider the idle state of the whole core for load balance

Tim C Chen (5):
  sched/fair: Determine active load balance for SMT sched groups
  sched/topology: Record number of cores in sched group
  sched/fair: Implement prefer sibling imbalance calculation between
    asymmetric groups
  sched/x86: Add cluster topology to hybrid CPU
  sched/debug: Dump domains' sched group flags

 arch/x86/kernel/smpboot.c |   3 +
 kernel/sched/debug.c      |   1 +
 kernel/sched/fair.c       | 151 ++++++++++++++++++++++++++++++++++++--
 kernel/sched/sched.h      |   6 ++
 kernel/sched/topology.c   |  10 ++-
 5 files changed, 165 insertions(+), 6 deletions(-)

-- 
2.32.0


             reply	other threads:[~2023-06-08 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 22:32 Tim Chen [this message]
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
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=cover.1686263351.git.tim.c.chen@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;
as well as URLs for NNTP newsgroup(s).