From: Tim Chen <tim.c.chen@linux.intel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
linux-kernel@vger.kernel.org
Cc: joel@joelfernandes.org
Subject: Re: [PATCH 0/2] avoid spurious blocked load update
Date: Tue, 16 Nov 2021 15:48:40 -0800 [thread overview]
Message-ID: <41d0d7cbd3e292eb89b12d27d9beb576be3531bf.camel@linux.intel.com> (raw)
In-Reply-To: <20211112095857.7016-1-vincent.guittot@linaro.org>
On Fri, 2021-11-12 at 10:58 +0100, Vincent Guittot wrote:
> This patchset is a follow up of :
> https://lore.kernel.org/lkml/20211019123537.17146-1-vincent.guittot@linaro.org/
>
> It ensures that newly idle load balance will not kick the update of
> blocked load if it skips the load balance because avg_idle is too
> short.
> It also makes sure that rq->next_balance doesn't go in the past when
> updated.
>
> Tim Chen (1):
> sched: sched: Fix rq->next_balance time updated to earlier than
> current time
>
> Vincent Guittot (1):
> sched/fair: skip newidle update stats
>
> kernel/sched/fair.c | 25 ++++++++++++++++++++-----
> 1 file changed, 20 insertions(+), 5 deletions(-)
>
Vincent,
Got some data back from the benchmark team.
To my surprise, the skip_new_idle_update_stats patch
actually makes things a little worse.
Relative Performance
(higher better)
5.15 rc4 vanilla (cgroup disabled) 100%
5.15 rc4 vanilla (cgroup enabled) 96%
patch v2 96%
patch v3 96%
patch v3
+skip_new_idle_update_stats 93.7%
patch v3
+skip_new_idle_update_stats
+Fix rq->next_balance_time 93.7%
The cpu utilization actually is the similar compared with
having just the v3 patch. In both cases they are
81% user
12% kernel
2% idle
5% waiting for IO
Profile on key functions
in load balancing shows a little more cpu utilization,
which is unexpected as we are cutting short
the newidle_balance.
patch v3
0.56% [k] __update_load_avg_cfs_rq
0.51% [k] update_load_avg
0.39% [k] update_blocked_averages
0.36% [k] __update_load_avg_se
0.05% [k] newidle_balance
patch v3 + skip_new_idle_update_stats
0.58% [k] __update_load_avg_cfs_rq
0.53% [k] update_load_avg
0.40% [k] update_blocked_averages
0.37% [k] __update_load_avg_se
0.06% [k] newidle_balance
Context switch frequency is lower by 4% with the skip_new_idle_update_stats
patch.
Thanks.
Tim
next prev parent reply other threads:[~2021-11-16 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 9:58 [PATCH 0/2] avoid spurious blocked load update Vincent Guittot
2021-11-12 9:58 ` [PATCH 1/2] sched/fair: skip newidle update stats Vincent Guittot
2021-11-12 14:29 ` Peter Zijlstra
2021-11-12 14:47 ` Vincent Guittot
2021-11-12 15:29 ` Peter Zijlstra
2021-11-12 16:00 ` Vincent Guittot
2021-11-12 14:55 ` Peter Zijlstra
2021-11-12 14:55 ` Peter Zijlstra
2021-11-12 16:05 ` Vincent Guittot
2021-11-16 23:48 ` Tim Chen [this message]
2021-11-18 14:40 ` [PATCH 0/2] avoid spurious blocked load update Vincent Guittot
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=41d0d7cbd3e292eb89b12d27d9beb576be3531bf.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--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=vincent.guittot@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.