From: Rik van Riel <riel@surriel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Mel Gorman <mgorman@suse.de>,
Valentin Schneider <valentin.schneider@arm.com>
Subject: Re: [PATCH v3] sched,fair: skip newidle_balance if a wakeup is pending
Date: Thu, 22 Apr 2021 12:47:01 -0400 [thread overview]
Message-ID: <416c515026af10cc913a83bc72c18aeb296c6583.camel@surriel.com> (raw)
In-Reply-To: <CAKfTPtBogNs1uVoTmiNj0Xw57ZsJ0DS-pas-gA67E79CXvHR5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Thu, 2021-04-22 at 10:37 +0200, Vincent Guittot wrote:
> On Wed, 21 Apr 2021 at 19:27, Vincent Guittot
> <vincent.guittot@linaro.org> wrote:
> >
> > > - if (pulled_task)
> > > + /*
> > > + * If we are no longer idle, do not let the time spent
> > > here pull
> > > + * down this_rq->avg_idle. That could lead to
> > > newidle_balance not
> > > + * doing enough work, and the CPU actually going idle.
> > > + */
> > > + if (pulled_task || this_rq->ttwu_pending)
> >
> I confirmed that the line above generate hackbench regression on my
> large arm64 system (2 * 112 CPUs)
> I'm testing hackbench with various number of group : 1, 2, 4, 16, 32,
> 64, 128, 256 but I have only put the 2 results which significantly
> regress. The other ones are in the +/-1% variation range
>
> hackbench -g $group
>
> group v5.12-rc8+tip w/ this patch w/ this patch
> without
> the line above
> 64 2.862(+/- 9%) 2.952(+/-11%) -3% 2.807(+/- 7%) +2%
> 128 3.334(+/-10%) 3.561-+/-13%) -7% 3.181(+/- 6%) +4%
OK, I guess this part of the patch needs additional work.
I'll send a v4 with just the first two changes.
Thank you for running those tests.
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-22 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 16:07 Rik van Riel
2021-04-21 17:27 ` Vincent Guittot
2021-04-22 8:37 ` Vincent Guittot
2021-04-22 16:47 ` Rik van Riel [this message]
2021-04-22 7:36 ` [tip: sched/core] " tip-bot2 for Rik van Riel
2021-04-22 8:15 ` Peter Zijlstra
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=416c515026af10cc913a83bc72c18aeb296c6583.camel@surriel.com \
--to=riel@surriel.com \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--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 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®