From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
"Chen, Yu C" <yu.c.chen@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Doug Nelson <doug.nelson@intel.com>,
Mohini Narkhede <mohini.narkhede@intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Skip useless sched_balance_running acquisition if load balance is not due
Date: Fri, 18 Apr 2025 10:56:04 +0530 [thread overview]
Message-ID: <87728994-b928-45b3-a6a0-258af6e81294@amd.com> (raw)
In-Reply-To: <20250417120130.GE17910@noisy.programming.kicks-ass.net>
Hello Peter,
On 4/17/2025 5:31 PM, Peter Zijlstra wrote:
>> o Since this is a single flag across the entire system, it also implies
>> CPUs cannon concurrently do load balancing across different NUMA
>> domains which seems reasonable since a load balance at lower NUMA
>> domain can potentially change the "nr_numa_running" and
>> "nr_preferred_running" stats for the higher domain but if this is the
>> case, a newidle balance at lower NUMA domain can interfere with a
>> concurrent busy / newidle load balancing at higher NUMA domain.
>> Is this expected? Should newidle balance be serialized too?
>
> Serializing new-idle might create too much idle time.
In the context of busy and idle balancing, What are your thoughts on a
per sd "serialize' flag?
>
>> (P.S. I copied over the serialize logic from sched_balance_domains()
>> into sched_balance_newidle() and did not see any difference in my
>> testing but perhaps there are benchmarks out there that care for
>> this)
>>
>> o If the intention of SD_SERIALIZE was to actually "serializes
>> load-balancing passes over large domains (above the NODE topology
>> level)" as the comment above "sched_balance_running" states, and
>> this question is specific to x86 - when enabling SNC on Intel or
>> NPS on AMD servers, the first NUMA domain is in fact as big as the
>> NODE (now PKG domain) if not smaller. Is it okay to clear
>> SD_SERIALIZE for these domains since they are small enough now?
>
> You'll have to dive into the history here, but IIRC it was from SGI back
> in the day, where NUMA factors were quite large and load-balancing
> across numa was a pain.
Let me dig up the git history and see if any interesting details hide
there.
>
> Small really isn't the criteria, but inter-node latency might be, we
> also have this node_reclaim_distance thing.
>
> Not quite sure what makes sense, someone should tinker I suppose, see
> what works with today's hardare.
I'll try some experiments over the weekend to see if my machine turns
up happy with non-serialized lb for inter-PKG load balancing with NPS
turned on. I'll probably piggy back off of "node_reclaim_distance"
heuristics.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2025-04-18 5:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 3:58 Tim Chen
2025-04-16 5:30 ` Shrikanth Hegde
2025-04-16 6:28 ` Chen, Yu C
2025-04-16 9:16 ` Shrikanth Hegde
2025-04-16 9:29 ` Shrikanth Hegde
2025-04-16 9:47 ` Vincent Guittot
2025-04-16 14:14 ` Shrikanth Hegde
2025-04-17 11:10 ` K Prateek Nayak
2025-04-18 15:02 ` Vincent Guittot
2025-04-18 17:55 ` Shrikanth Hegde
2025-04-17 11:31 ` K Prateek Nayak
2025-04-17 12:01 ` Peter Zijlstra
2025-04-18 5:26 ` K Prateek Nayak [this message]
2025-04-18 9:28 ` Peter Zijlstra
2025-04-18 12:13 ` K Prateek Nayak
2025-04-16 16:19 ` Tim Chen
2025-04-16 17:11 ` Shrikanth Hegde
2025-04-17 9:19 ` Shrikanth Hegde
2025-04-17 17:12 ` Tim Chen
2025-05-29 9:00 ` K Prateek Nayak
2025-06-04 4:26 ` Chen, Yu C
2025-06-06 13:51 ` Vincent Guittot
2025-10-27 18:06 ` Mel Gorman
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=87728994-b928-45b3-a6a0-258af6e81294@amd.com \
--to=kprateek.nayak@amd.com \
--cc=doug.nelson@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mohini.narkhede@intel.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=tim.c.chen@linux.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®