From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Wangyang Guo <wangyang.guo@intel.com>
Cc: linux-kernel@vger.kernel.org,
Benjamin Lei <benjamin.lei@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Tianyou Li <tianyou.li@intel.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH] sched/fair: Avoid false sharing in nohz struct
Date: Sun, 21 Dec 2025 18:35:03 +0530 [thread overview]
Message-ID: <c2ba13e1-f25b-4b31-b231-b035ffd727b3@linux.ibm.com> (raw)
In-Reply-To: <20251211055612.4071266-1-wangyang.guo@intel.com>
Hi Wangyang,
On 12/11/25 11:26 AM, Wangyang Guo wrote:
> There are two potential false sharing issue in nohz struct:
> 1. idle_cpus_mask is a read-mostly field, but share the same cacheline
> with frequently updated nr_cpus.
Updates to idle_cpus_mask is not same cacheline. it is updated alongside nr_cpus.
with CPUMASK_OFFSTACK=y, idle_cpus_mask is a pointer to the actual mask.
Updates to it happen in another cacheline.
with CPUMASK_OFFSTACK=n, idle_cpus_mask is on the stack and its length
depends on NR_CPUS. typical value being 512/2048/8192 it can span a few
cachelines. So updates to it likely in different cacheline compared to nr_cpus.
see https://lore.kernel.org/all/aS6bK4ad-wO2fsoo@gmail.com/
Likely in your case, nr_cpus updates are the costly ones.
Try below and see if it helps to fix your issue too.
https://lore.kernel.org/all/20251201183146.74443-1-sshegde@linux.ibm.com/
I Should send out new version soon.
> 2. Data followed by nohz still share the same cacheline and has
> potential false sharing issue.
>
How does your patch handle this?
I don't see any other struct apart from nohz being changed.
> This patch tries to resolve the above two problems by isolating the
> frequently updated fields in a single cacheline.
>
> Reported-by: Benjamin Lei <benjamin.lei@intel.com>
> Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
> Reviewed-by: Tianyou Li <tianyou.li@intel.com>
> Signed-off-by: Wangyang Guo <wangyang.guo@intel.com>
> ---
> kernel/sched/fair.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 5b752324270b..bcc2766b7986 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -7193,13 +7193,14 @@ static DEFINE_PER_CPU(cpumask_var_t, should_we_balance_tmpmask);
> #ifdef CONFIG_NO_HZ_COMMON
>
> static struct {
> - cpumask_var_t idle_cpus_mask;
> - atomic_t nr_cpus;
> + /* Isolate frequently updated fields in a cacheline to avoid false sharing issue. */
> + atomic_t nr_cpus ____cacheline_aligned;
> int has_blocked; /* Idle CPUS has blocked load */
> int needs_update; /* Newly idle CPUs need their next_balance collated */
> unsigned long next_balance; /* in jiffy units */
> unsigned long next_blocked; /* Next update of blocked load in jiffies */
> -} nohz ____cacheline_aligned;
> + cpumask_var_t idle_cpus_mask ____cacheline_aligned;
> +} nohz;
>
This can cause a lot of space wastage.
for exp: powerpc has 128 byte cacheline.
next prev parent reply other threads:[~2025-12-21 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 5:56 [PATCH] sched/fair: Avoid false sharing in nohz struct Wangyang Guo
2025-12-21 13:05 ` Shrikanth Hegde [this message]
2025-12-22 2:21 ` Guo, Wangyang
2025-12-23 7:27 ` Shrikanth Hegde
2025-12-23 8:03 ` Guo, Wangyang
-- strict thread matches above, loose matches on Subject: below --
2025-12-19 1:38 Shubhang Kaushik Prasanna Kumar
2025-12-19 13:56 ` Guo, Wangyang
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=c2ba13e1-f25b-4b31-b231-b035ffd727b3@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=benjamin.lei@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@linux.intel.com \
--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