From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: <christophe.leroy@csgroup.eu>, <linux-kernel@vger.kernel.org>,
<ritesh.list@gmail.com>, <kprateek.nayak@amd.com>,
<vineethr@linux.ibm.com>, <vincent.guittot@linaro.org>,
<srikar@linux.ibm.com>, <npiggin@gmail.com>, <mpe@ellerman.id.au>,
<maddy@linux.ibm.com>, <linuxppc-dev@lists.ozlabs.org>,
<peterz@infradead.org>
Subject: Re: [PATCH 0/4] powerpc/topology: Introduce llc_override debugfs
Date: Tue, 13 Oct 2026 18:05:08 +0800 [thread overview]
Message-ID: <51744944-51c2-4989-8ca8-41a8c53ed1e2@intel.com> (raw)
In-Reply-To: <0cbd60fcf328ffcb317739f60d327da3af6145f1.camel@linux.intel.com>
On 10/13/2026 5:15 AM, Tim Chen wrote:
> On Mon, 2026-10-12 at 15:50 +0530, Shrikanth Hegde wrote:
[ ... ]
>>
>> Tim, Chenyu, Peter,
>> Are there any selftest or patches which is used for
>> functional validation of cache aware scheduling?
>
> We haven't created one. We validate mostly with workloads such as
> hackbench, schbench and yogini (which can vary the number of threads
> over time and track CPU assignment). I agree they are not ideal for
> functional checks of the load balance path.
>
>> per-LLC occupancy in /proc/{PID}/schedstat may not tell the full
>> story when there are multiple processes and multiple LLC's.
>>
>> Atleast for functional verification, we might need one if there is
>> not one already. The reason being,
>> - At present, we may need a custom workload. hackbench/schbench are
>> wakeup intensive and typically bail out even before load balance.
>> - stress-ng is per process. So doesn't get cache aware scheduling.
>> - A selftest could spwan specific number of threads till llc size etc
>> and ensure packing happens till core_count(llc_size) by default.
>> This could also be used for tunable verfifications.
>> - Provide an ability to observe how much of the workload was contained
>> within the LLC due to cache aware scheduling or number of load
>> balances stopped due to preferred llc.
>
> A selftest would be great and much welcomed.
>
Yes, that would be very useful. For functional testing, previously we
asked AI to generate a trial test script to launch a random number of
while(1) tests and watch their occupancy on each LLC.
thanks,
Chenyu
prev parent reply other threads:[~2026-10-13 10:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 10:20 Shrikanth Hegde
2026-10-12 10:20 ` [PATCH 1/4] powerpc/topology: Introduce llc_override debug knob Shrikanth Hegde
2026-10-12 12:14 ` Srikar Dronamraju
2026-10-12 14:10 ` Shrikanth Hegde
2026-10-12 10:20 ` [PATCH 2/4] powerpc/topology: Add docs for llc_override Shrikanth Hegde
2026-10-12 10:20 ` [PATCH 3/4] powerpc/topology: Update mc/pkg flags based on llc_override Shrikanth Hegde
2026-10-12 10:20 ` [PATCH 4/4] powerpc/topology: Rebuild sched domains on llc_override change Shrikanth Hegde
2026-10-12 12:19 ` [PATCH 0/4] powerpc/topology: Introduce llc_override debugfs Srikar Dronamraju
2026-10-12 14:14 ` Shrikanth Hegde
2026-10-12 21:15 ` Tim Chen
2026-10-13 9:58 ` Shrikanth Hegde
2026-10-13 20:44 ` Tim Chen
2026-10-14 3:16 ` Shrikanth Hegde
2026-10-14 3:56 ` Srikar Dronamraju
2026-10-14 4:18 ` Shrikanth Hegde
2026-10-13 10:05 ` Chen, Yu C [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=51744944-51c2-4989-8ca8-41a8c53ed1e2@intel.com \
--to=yu.c.chen@intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.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®