From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org
Cc: sshegde@linux.ibm.com, kprateek.nayak@amd.com,
juri.lelli@redhat.com, vschneid@redhat.com, tglx@kernel.org,
dietmar.eggemann@arm.com, anna-maria@linutronix.de,
frederic@kernel.org, wangyang.guo@intel.com
Subject: [PATCH v4 0/3] sched/fair: Improve nohz fields for large systems
Date: Mon, 12 Jan 2026 10:34:39 +0530 [thread overview]
Message-ID: <20260112050442.138446-1-sshegde@linux.ibm.com> (raw)
Running on large systems nohz.nr_cpus cacheline was seen as contended.
There is atomic inc/dec and read happening on many
CPUs at a time and it is possible for this line to bounce often.
1st and 2nd patch are minor ones. Looks like correct things to do.
Not very important ones.
3rd patch: Main patch which is to get rid of nr_cpus.Instead, use the cpumask
which is always updated alongside with it. Functionally it should serve
the same purpose. Rest of the fields aren't updated that often. So this
line shouldn't bounce that often.
Contention issue with nohz.idle_cpus_mask still remains. Mostly it is in
separate cacheline than nohz. There are ongoing efforts to mitigate it. It
is not addressed by this series.
v3 -> v4:
- Added to changelog on one less cacheline being dirtied on idle
entry/exit (Valentin Schneider)
v2 -> v3:
- Converted out to return when there are no CPU is in tickless mode
since find_ilb_cpu returns anyway (K Prateek Nayak)
v1 -> v2:
- Dropped patch to check has_blocked based on time.
- Detailed changelog for removing nr_cpus (Thanks to Ingo Molnar)
v1: https://lore.kernel.org/all/20251201183146.74443-1-sshegde@linux.ibm.com/
v2: https://lore.kernel.org/all/20260102124744.360872-1-sshegde@linux.ibm.com/
v3: https://lore.kernel.org/all/20260107065125.669668-1-sshegde@linux.ibm.com/
Shrikanth Hegde (3):
sched/fair: Move checking for nohz cpus after time check
sched/fair: Change likelyhood of nohz.nr_cpus
sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead
kernel/sched/fair.c | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-12 5:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 5:04 Shrikanth Hegde [this message]
2026-01-12 5:04 ` [PATCH v4 1/3] sched/fair: Move checking for nohz cpus after time check Shrikanth Hegde
2026-01-13 9:07 ` Vincent Guittot
2026-01-13 9:23 ` Shrikanth Hegde
2026-01-13 10:21 ` Vincent Guittot
2026-01-13 11:18 ` Shrikanth Hegde
2026-01-13 13:20 ` Vincent Guittot
2026-01-12 5:04 ` [PATCH v4 2/3] sched/fair: Change likelyhood of nohz.nr_cpus Shrikanth Hegde
2026-01-12 5:04 ` [PATCH v4 3/3] sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead Shrikanth Hegde
2026-01-12 11:49 ` Valentin Schneider
2026-01-13 9:23 ` Vincent Guittot
2026-01-13 9:30 ` Shrikanth Hegde
2026-01-13 6:45 ` [PATCH v4 0/3] sched/fair: Improve nohz fields for large systems K Prateek Nayak
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=20260112050442.138446-1-sshegde@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=anna-maria@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangyang.guo@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®