From: Peter Zijlstra <peterz@infradead.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Deng Pan <pan.deng@intel.com>,
tim.c.chen@intel.com, vincent.guittot@linaro.org,
linux-kernel@vger.kernel.org, tianyou.li@intel.com,
yu.ma@intel.com, lipeng.zhu@intel.com, yu.c.chen@intel.com,
Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: [PATCH v2] sched/task_group: Re-layout structure to reduce false sharing
Date: Tue, 27 Jun 2023 12:14:37 +0200 [thread overview]
Message-ID: <20230627101437.GY4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230626054756.GA435374@ziqianlu-dell>
On Mon, Jun 26, 2023 at 01:47:56PM +0800, Aaron Lu wrote:
> > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> > index ec7b3e0a2b20..4fbd4b3a4bdd 100644
> > --- a/kernel/sched/sched.h
> > +++ b/kernel/sched/sched.h
> > @@ -389,6 +389,19 @@ struct task_group {
> > #endif
> > #endif
> >
> > + struct rcu_head rcu;
> > + struct list_head list;
> > +
> > + struct list_head siblings;
> > + struct list_head children;
> > +
> > + /*
> > + * To reduce false sharing, current layout is optimized to make
> > + * sure load_avg is in a different cacheline from parent, rt_se
> > + * and rt_rq.
> > + */
That comment is misleading I think; you don't particularly care about
those fields more than any other active fields that would cause false
sharing.
> > + struct task_group *parent;
> > +
>
> I wonder if we can simply do:
>
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index ec7b3e0a2b20..31b73e8d9568 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -385,7 +385,9 @@ struct task_group {
> * it in its own cacheline separated from the fields above which
> * will also be accessed at each tick.
> */
> - atomic_long_t load_avg ____cacheline_aligned;
> + struct {
> + atomic_long_t load_avg;
> + } ____cacheline_aligned_in_smp;
> #endif
> #endif
>
> This way it can make sure there is no false sharing with load_avg no
> matter how the layout of this structure changes in the future.
This. Also, ISTR there was a series to split this atomic across nodes;
whatever happend to that, and can we still measure an improvement over
this with that approach?
next prev parent reply other threads:[~2023-06-27 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 8:14 Deng Pan
2023-06-26 5:47 ` Aaron Lu
2023-06-26 7:52 ` Chen Yu
2023-06-26 12:53 ` Aaron Lu
2023-06-27 8:05 ` Chen Yu
2023-06-27 10:10 ` Peter Zijlstra
2023-06-26 17:09 ` Tim Chen
2023-06-27 8:08 ` Chen Yu
2023-06-27 14:52 ` Deng, Pan
2023-06-26 12:51 ` Deng, Pan
2023-06-27 10:14 ` Peter Zijlstra [this message]
2023-06-27 16:12 ` Deng, Pan
2023-07-06 14:05 ` Deng, Pan
2023-06-28 5:18 ` Aaron Lu
2023-06-30 9:35 ` Aaron Lu
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=20230627101437.GY4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aaron.lu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng.zhu@intel.com \
--cc=pan.deng@intel.com \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=yu.c.chen@intel.com \
--cc=yu.ma@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®