From: Tim Chen <tim.c.chen@linux.intel.com>
To: Klaus Kusche <klaus.kusche@computerix.info>,
Chen Yu <yu.c.chen@intel.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
"Badole, Vishal" <Vishal.Badole@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
platform-driver-x86@vger.kernel.org,
K Prateek Nayak <KPrateek.Nayak@amd.com>,
ricardo.neri@intel.com
Subject: Re: Cache-aware scheduling does not work well with amd big/little cores
Date: Mon, 28 Sep 2026 10:22:02 -0700 [thread overview]
Message-ID: <2e64c909e48087b188b8220344ef6576bd273373.camel@linux.intel.com> (raw)
In-Reply-To: <c3e26de1-85de-4b44-8498-9878e95f4d5c@computerix.info>
On Sun, 2026-09-27 at 12:47 +0200, Klaus Kusche wrote:
> Hello,
>
> this one looks good.
> It does not show any core assignment anomalies
> in the core bar graph (i.e. no processes are staying
> on little cores when big cores are idle),
> and at least for the two compile jobs I tested,
> it gives timings which are
>
> * better w.r.t. elapsed wallclock time
> (sometimes slightly, sometimes significantly)
> than all other versions and patches I tried so far
> with cache-aware scheduling on
>
> * and at least as good as the unpatched kernel
> with cache-aware scheduling turned off
> (so one does not loose anything by turning it on).
Thank you for testing and sharing the results so quickly.
I will send a cleaned up patch for sched/urgent branch shortly for
Peter.
Tim
>
> As expected, the uv build profits more than the kernel built,
> because besides all-cores-loaded and single-core-loaded phases,
> it spends significant time with about half as many busy processes
> as cores, and in these phases, placement makes a difference.
>
> Klaus Kusche
>
prev parent reply other threads:[~2026-09-28 17:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 15:42 Klaus Kusche
2026-08-31 1:53 ` Mario Limonciello
2026-08-31 2:08 ` Chen, Yu C
2026-08-31 11:24 ` Klaus Kusche
2026-08-31 17:29 ` Tim Chen
2026-08-31 18:49 ` Klaus Kusche
2026-08-31 18:53 ` Mario Limonciello
2026-09-05 15:40 ` Klaus Kusche
2026-09-08 21:54 ` Tim Chen
2026-09-09 8:59 ` Klaus Kusche
2026-09-09 13:19 ` Mario Limonciello
2026-09-09 19:51 ` Tim Chen
2026-09-10 1:29 ` Chen, Yu C
2026-09-14 10:27 ` Klaus Kusche
2026-09-14 13:13 ` Chen Yu
2026-09-16 14:52 ` Klaus Kusche
2026-09-23 23:47 ` Tim Chen
2026-09-25 8:59 ` Klaus Kusche
2026-09-25 19:19 ` Tim Chen
2026-09-27 10:47 ` Klaus Kusche
2026-09-28 17:22 ` Tim Chen [this message]
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=2e64c909e48087b188b8220344ef6576bd273373.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=KPrateek.Nayak@amd.com \
--cc=Vishal.Badole@amd.com \
--cc=klaus.kusche@computerix.info \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ricardo.neri@intel.com \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®