From: Peter Zijlstra <peterz@infradead.org>
To: Li Zetao <lizetao1@huawei.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, zhangqiao22@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] sched/fair: inline cpu_util_without and cpu_util to improve performance
Date: Wed, 24 Jul 2024 12:53:38 +0200 [thread overview]
Message-ID: <20240724105338.GA13387@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240723073607.568819-1-lizetao1@huawei.com>
On Tue, Jul 23, 2024 at 03:36:07PM +0800, Li Zetao wrote:
> The commit 3eb6d6ececca ("sched/fair: Refactor CPU utilization functions")
> refactored cpu_util_without and cpu_util functions. Since the size of
> cpu_util function has increased, the inline cpu_util is dropped. This had
> a negative impact on performance, in the scenario of updating
> sched_group's statistics, cpu_util_without and cpu_util functions are on
> the hotspot path.
>
> Inlining cpu_util_without and cpu_util functions have been shown to
> significantly improve performance in lmbench as follow:
>
> Machine: Intel(R) Xeon(R) Gold 6248 CPU @ 2.50GHz
> before after diff
> fork+exit 317.0625 303.6667 -4.22%
> fork+execve 1482.5000 1407.0000 -5.09%
> fork+/bin/sh 2096.0000 2020.3333 -3.61%
That's quite significant. Did you look at what exactly was causing this?
> This patch introduces inlining to cpu_util_without and cpu_util functions.
> While this increases the size of kernel/sched/fair.o, the performance
> gains in critical workloads make this an acceptable trade-off.
>
> Size comparison before and after patch:
> text data bss dec hex filename
> 0x1264a 0x1506 0xb0 80896 13c00 kernel/sched/fair.o.before
> 0x12672 0x14fe 0xb0 80928 13c20 kernel/sched/fair.o.after
>
> Signed-off-by: Zhang Qiao <zhangqiao22@huawei.com>
> Signed-off-by: Li Zetao <lizetao1@huawei.com>
This SoB chain is not valid. Please review the documentation we have
on this.
> ---
> kernel/sched/fair.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 5904405ffc59..677b78fa65b6 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -7706,7 +7706,7 @@ static int select_idle_sibling(struct task_struct *p, int prev, int target)
> *
> * Return: (Boosted) (estimated) utilization for the specified CPU.
> */
> -static unsigned long
> +static __always_inline unsigned long
> cpu_util(int cpu, struct task_struct *p, int dst_cpu, int boost)
> {
> struct cfs_rq *cfs_rq = &cpu_rq(cpu)->cfs;
> @@ -7794,7 +7794,7 @@ unsigned long cpu_util_cfs_boost(int cpu)
> * utilization of the specified task, whenever the task is currently
> * contributing to the CPU utilization.
> */
> -static unsigned long cpu_util_without(int cpu, struct task_struct *p)
> +static __always_inline unsigned long cpu_util_without(int cpu, struct task_struct *p)
> {
> /* Task has no contribution or is new */
> if (cpu != task_cpu(p) || !READ_ONCE(p->se.avg.last_update_time))
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-07-24 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 7:36 [PATCH -next] sched/fair: inline cpu_util_without and cpu_util to improve performance Li Zetao
2024-07-24 10:53 ` Peter Zijlstra [this message]
2024-07-25 14:16 ` Li Zetao
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=20240724105338.GA13387@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhangqiao22@huawei.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