From: Peter Zijlstra <peterz@infradead.org>
To: Kyle Meyer <kyle.meyer@hpe.com>
Cc: tim.c.chen@linux.intel.com, bp@alien8.de,
dave.hansen@linux.intel.com, mingo@redhat.com, tglx@kernel.org,
vinicius.gomes@intel.com, brgerst@gmail.com, hpa@zytor.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
patryk.wlazlyn@linux.intel.com, rafael.j.wysocki@intel.com,
russ.anderson@hpe.com, x86@kernel.org, yu.c.chen@intel.com,
zhao1.liu@intel.com
Subject: Re: [PATCH v2] sched/topology: Check average distances to remote packages
Date: Wed, 25 Feb 2026 17:49:16 +0100 [thread overview]
Message-ID: <20260225164916.GE1282955@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aZ8mQkRtNSgFGdVv@hpe.com>
On Wed, Feb 25, 2026 at 10:41:38AM -0600, Kyle Meyer wrote:
> On Wed, Feb 25, 2026 at 01:30:52PM +0100, Peter Zijlstra wrote:
> > The original case was for SNC-3, the above looks to be SNC-2. Does your
> > system also support SNC-3?
>
> We do not currently use SKUs that support SNC-3.
>
> That distance would be set to 12:
>
> node 0 1 2
> 0: 10 12 12
> 1: 12 10 12
> 2: 12 12 10
>
> That might be changed if there's actually a difference in distance.
>
> Distances to adjacent sockets, non-adjacent sockets, and different chassis would
> remain the same.
OK, excellent. So its just the Intel reference systems that are crazy.
prev parent reply other threads:[~2026-02-25 16:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 0:24 [PATCH v2] sched/topology: Check average distances to remote packages Kyle Meyer
2026-02-23 16:42 ` Kyle Meyer
2026-02-23 17:03 ` Peter Zijlstra
2026-02-25 1:43 ` Kyle Meyer
2026-02-25 9:05 ` Chen, Yu C
2026-02-25 12:30 ` Peter Zijlstra
2026-02-25 13:36 ` Peter Zijlstra
2026-02-25 15:39 ` Chen, Yu C
2026-02-25 15:44 ` Peter Zijlstra
2026-02-25 16:32 ` Peter Zijlstra
2026-02-25 16:40 ` Peter Zijlstra
2026-02-25 21:37 ` Tim Chen
2026-02-25 22:30 ` Peter Zijlstra
2026-02-25 22:54 ` Peter Zijlstra
2026-02-25 22:55 ` Tim Chen
2026-02-25 23:29 ` Kyle Meyer
2026-02-26 18:14 ` Tim Chen
2026-02-25 16:41 ` Kyle Meyer
2026-02-25 16:49 ` Peter Zijlstra [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=20260225164916.GE1282955@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kprateek.nayak@amd.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patryk.wlazlyn@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=russ.anderson@hpe.com \
--cc=tglx@kernel.org \
--cc=tim.c.chen@linux.intel.com \
--cc=vinicius.gomes@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.com \
--cc=zhao1.liu@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