mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: KobaK <kobak@nvidia.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Chen Yu	 <yu.c.chen@intel.com>,
	Ricardo Neri <ricardo.neri@intel.com>,
	Len Brown	 <len.brown@intel.com>, Aubrey Li <aubrey.li@intel.com>,
		linux-kernel@vger.kernel.org,
	Ricardo Neri	 <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH] sched/fair: avoid creating misfits during cache-aware balancing
Date: Mon, 14 Sep 2026 12:51:00 -0700	[thread overview]
Message-ID: <670e5ffe0964f075ed96e2104d3b25bb4ece5143.camel@linux.intel.com> (raw)
In-Reply-To: <20260914025949.1348528-1-kobak@nvidia.com>

On Mon, 2026-09-14 at 10:59 +0800, KobaK wrote:
> Hi Tim,
> 
> Thanks for the cache-aware load-balancing misfit patch. The tradeoff
> you describe (LLC locality vs capacity loss) is clear.
> 
> I have been trying to understand how this showed up in testing. The
> cover explains the failure mode, but I did not find a note on the
> observation method.
> 
> Would you mind sharing how you tested and observed it? In particular:
> which hybrid generation, what workload, and whether you used
> schedstat lb_imbalance_misfit or another signal.
> 
> Thanks,
> Koba

Kobak,

My colleague Ricardo was doing tests on the Nova Lake CPU which has
LP-E cores on one LLC domain and the E-cores/P-cores on
other LLC domain. He pinned a process with
threads on the LP-E cores and then unpin it.

His expectation was that the process should move to
the more capable cores but that did
not happen because cache aware scheduling took precedent.
So the patch was meant to fix this behavior.
This can be seen easily with mpstat.

Cc Ricardo here and he can provide more details if you
are interested.

Tim


      reply	other threads:[~2026-09-14 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 17:41 Tim Chen
2026-08-26 15:57 ` Tim Chen
2026-08-31  8:41 ` Peter Zijlstra
2026-08-31 17:17   ` Tim Chen
2026-08-31 17:40   ` Tim Chen
2026-09-02  7:21     ` [tip: sched/urgent] sched/fair: Avoid " tip-bot2 for Tim Chen
2026-09-14  2:59 ` [PATCH] sched/fair: avoid " KobaK
2026-09-14 19:51   ` 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=670e5ffe0964f075ed96e2104d3b25bb4ece5143.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=aubrey.li@intel.com \
    --cc=kobak@nvidia.com \
    --cc=kprateek.nayak@amd.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=ricardo.neri@intel.com \
    --cc=vincent.guittot@linaro.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®