public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: stable@vger.kernel.org
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Chen Yu <yu.c.chen@intel.com>,
	Doug Nelson <doug.nelson@intel.com>,
	Mohini Narkhede <mohini.narkhede@intel.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	nathan@kernel.org
Subject: [PATCH 6.18 0/2] Acquire sched_balance_running only when needed
Date: Thu,  5 Feb 2026 13:31:55 -0800	[thread overview]
Message-ID: <cover.1770326432.git.tim.c.chen@linux.intel.com> (raw)

Balancing sched domains NUMA and above are serialized.
Currently, multiple sched group leader directly under NUMA domain could
attempt to acquire the global sched_balance_running flag via cmpxchg() before
checking whether load balancing is due. Fix unnecessary
sched_balance_running acquisition and also put newidle balance
properly in serialization.  This improves performance for OLTP workload
on large core count machines.

These patches have been merged upstream.

Thanks.

Tim

Peter Zijlstra (1):
  sched/fair: Have SD_SERIALIZE affect newidle balancing

Tim Chen (1):
  sched/fair: Skip sched_balance_running cmpxchg when balance is not due

 kernel/sched/fair.c | 54 +++++++++++++++++++++++----------------------
 1 file changed, 28 insertions(+), 26 deletions(-)

-- 
2.32.0


             reply	other threads:[~2026-02-05 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 21:31 Tim Chen [this message]
2026-02-05 21:31 ` [PATCH 6.18 1/2] sched/fair: Skip sched_balance_running cmpxchg when balance is not due Tim Chen
2026-02-05 21:31 ` [PATCH 6.18 2/2] sched/fair: Have SD_SERIALIZE affect newidle balancing Tim 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=cover.1770326432.git.tim.c.chen@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=doug.nelson@intel.com \
    --cc=kprateek.nayak@amd.com \
    --cc=mingo@kernel.org \
    --cc=mohini.narkhede@intel.com \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --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