From: Peter Zijlstra <peterz@infradead.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Valentin Schneider <valentin.schneider@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org,
Gilles Muller <Gilles.Muller@inria.fr>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: SD_LOAD_BALANCE
Date: Mon, 12 Oct 2020 13:21:24 +0200 [thread overview]
Message-ID: <20201012112124.GT2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2010101740290.2691@hadrien>
On Sat, Oct 10, 2020 at 06:14:23PM +0200, Julia Lawall wrote:
> Prior to v5.8 on my machine this was a rare event, because there were not
> many of these background processes. But in v5.8, the default governor for
> Intel machines without the HWP feature was changed from intel_pstate to
> intel_cpufreq. The use of intel_cpufreq triggers very frequent kworkers on
> all cores, which makes it much more likely that cores that are currently
> idle, and are overall not at all overloaded, will have a higher load
> average even with the waking thread deducted, than the core managing the
> wakeup of the threads.
Rafael, any idea what those kworkers are for, and can we get rid of
them?
next prev parent reply other threads:[~2020-10-12 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:09 SD_LOAD_BALANCE Julia Lawall
2020-09-03 16:59 ` SD_LOAD_BALANCE Valentin Schneider
2020-09-03 17:10 ` SD_LOAD_BALANCE Julia Lawall
2020-09-03 18:17 ` SD_LOAD_BALANCE Julia Lawall
2020-10-10 16:14 ` SD_LOAD_BALANCE Julia Lawall
2020-10-12 10:16 ` SD_LOAD_BALANCE Vincent Guittot
2020-10-12 10:34 ` SD_LOAD_BALANCE Julia Lawall
2020-10-12 11:09 ` SD_LOAD_BALANCE Vincent Guittot
2020-10-12 11:18 ` SD_LOAD_BALANCE Julia Lawall
2020-10-12 11:21 ` Peter Zijlstra [this message]
2020-10-12 11:31 ` SD_LOAD_BALANCE Julia Lawall
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=20201012112124.GT2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Gilles.Muller@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--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®