From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<vschneid@redhat.com>, <linux-kernel@vger.kernel.org>,
<tim.c.chen@linux.intel.com>, <tglx@linutronix.de>,
<len.brown@intel.com>, <gautham.shenoy@amd.com>,
<mingo@kernel.org>, <yu.chen.surf@foxmail.com>
Subject: Re: [RFC][PATCH] sched: Cache aware load-balancing
Date: Thu, 27 Mar 2025 16:10:02 +0800 [thread overview]
Message-ID: <48cbfb23-aa4d-4e05-9a63-388a6ed6d9df@intel.com> (raw)
In-Reply-To: <20250326094242.GD25239@noisy.programming.kicks-ass.net>
On 3/26/2025 5:42 PM, Peter Zijlstra wrote:
> On Wed, Mar 26, 2025 at 05:15:24PM +0800, Chen, Yu C wrote:
>> Thanks for running the test. I think hackbenc/schbench would be the good
>> benchmarks to start with. I remember that you and Gautham mentioned that
>> schbench prefers to be aggregated in a single LLC in LPC2021 or 2022. I ran
>> a schbench test using mmtests on a Xeon server which has 4 NUMA nodes. Each
>> node has 80 cores (with SMT disabled). The numa=off option was appended to
>> the boot commandline, so there are 4 "LLCs" within each node.
>
> We really should look at getting the SnC topology even without SnC being
> in use.
>
I agree, unfortunately it seems that with SNC disabled there is no
information exposed to the OS that can be used to divide the large LLC
into smaller pieces.
thanks,
Chenyu
> The sheer size of these LLCs is untenable.
next prev parent reply other threads:[~2025-03-27 8:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 12:09 [RFC][PATCH] sched: Cache aware load-balancing Peter Zijlstra
2025-03-25 15:19 ` Chen, Yu C
2025-03-25 18:44 ` Peter Zijlstra
2025-03-26 6:18 ` K Prateek Nayak
2025-03-26 9:15 ` Chen, Yu C
2025-03-26 9:42 ` Peter Zijlstra
2025-03-27 8:10 ` Chen, Yu C [this message]
2025-03-26 9:38 ` Peter Zijlstra
2025-03-26 10:25 ` Peter Zijlstra
2025-03-26 10:42 ` Peter Zijlstra
2025-03-26 10:46 ` Peter Zijlstra
[not found] ` <20250327112059.3661-1-hdanton@sina.com>
2025-03-31 6:25 ` Chen, Yu C
2025-03-27 2:48 ` Chen, Yu C
2025-03-27 2:43 ` Madadi Vineeth Reddy
2025-03-27 11:14 ` Chen, Yu C
2025-03-31 20:17 ` Madadi Vineeth Reddy
2025-03-28 13:57 ` Abel Wu
2025-03-29 15:06 ` Chen, Yu C
2025-03-30 8:46 ` Abel Wu
2025-03-31 5:25 ` Chen, Yu C
2025-03-31 8:04 ` Abel Wu
2025-03-31 21:06 ` Tim Chen
2025-04-02 1:52 ` Libo 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=48cbfb23-aa4d-4e05-9a63-388a6ed6d9df@intel.com \
--to=yu.c.chen@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.chen.surf@foxmail.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