From: "Doug Smythies" <dsmythies@telus.net>
To: "'Giovanni Gherdovich'" <ggherdovich@suse.cz>
Cc: <x86@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"'Mel Gorman'" <mgorman@techsingularity.net>,
"'Matt Fleming'" <matt@codeblueprint.co.uk>,
"'Viresh Kumar'" <viresh.kumar@linaro.org>,
"'Juri Lelli'" <juri.lelli@redhat.com>,
"'Paul Turner'" <pjt@google.com>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Vincent Guittot'" <vincent.guittot@linaro.org>,
"'Quentin Perret'" <qperret@qperret.net>,
"'Dietmar Eggemann'" <dietmar.eggemann@arm.com>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Thomas Gleixner'" <tglx@linutronix.de>,
"'Ingo Molnar'" <mingo@redhat.com>,
"'Borislav Petkov'" <bp@suse.de>, "'Len Brown'" <lenb@kernel.org>,
"'Rafael J . Wysocki'" <rjw@rjwysocki.net>
Subject: RE: [PATCH v4 1/6] x86,sched: Add support for frequency invariance
Date: Tue, 26 Nov 2019 23:32:34 -0800 [thread overview]
Message-ID: <001d01d5a4f4$d96b21b0$8c416510$@net> (raw)
In-Reply-To: <1574781600.7677.2.camel@suse.cz>
On 2019.11.26 07:20 Giovanni Gherdovich wrote:
> On Mon, 2019-11-25 at 21:59 -0800, Doug Smythies wrote:
>> [...]
>> The issue with the schedutil governor not working properly in the 5.4 RC series
>> appears to be hardware dependant.
>>
>> My test computer is Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz., Sandy Bridge.
>> On a temporary basis, I acquired a computer with an
>> Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, Haswell,
>> and schedutil governor behaviour with the exact same kernels is fine:
>>
>> That "gitsource" test, "make test" 6 times, first run thrown out:
>>
>> Kernel 5.4 intel_cpufreq/schedutil: 3411.8 seconds
>> Kernel 5.4 + gg 6 intel_cpufreq/schedutil: 1696.7 seconds
>> Ratio: 0.49
>> Recall you got a ratio of 0.49 with 5th generation, Broadwell.
>
> It's good to hear that we're getting the same performance numbers for this
> patchset on all hardware that is not a Sandy Bridge. Thanks for double
> checking, independent verification is always valuable.
>
> Now, regarding the 5.4 regression for schedutil you see on Sandy Bridge: can
> we move this to the kernel bugzilla? Would you care to open a bug there and CC
> me to it?
O.K., I'll need another day or two to isolate further, then I'll open a bug.
I now understand considerably more, and why my bisection ended up
at a strange spot.
> If it's reproducible we should assess it and see what can be done.
On my Sandy Bridge system if the kernel configuration contains:
CONFIG_UCLAMP_TASK_GROUP=y
Then the intel_cpufreq/schedutil will respond much like the performance
governor.
If the kernel configuration contains:
# CONFIG_UCLAMP_TASK_GROUP is not set
Then the intel_cpufreq/schedutil will respond much like it used to.
On the Haswell computer, it doesn't seem to matter, and your tests
seem to confirm this.
Note: I steal my kernel configuration from the Ubuntu mainline builds,
and they changed this parameter during the 5.4-rc series.
... Doug
next prev parent reply other threads:[~2019-11-27 7:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:46 [PATCH v4 0/6] Add support for frequency invariance for (some) x86 Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 1/6] x86,sched: Add support for frequency invariance Giovanni Gherdovich
2019-11-24 7:49 ` Doug Smythies
2019-11-25 8:16 ` Doug Smythies
2019-11-25 9:16 ` Mel Gorman
2019-11-25 16:06 ` Giovanni Gherdovich
2019-11-26 5:59 ` Doug Smythies
2019-11-26 15:20 ` Giovanni Gherdovich
2019-11-27 7:32 ` Doug Smythies [this message]
2019-11-28 22:48 ` Doug Smythies
2019-12-19 10:48 ` Qais Yousef
2019-12-23 7:47 ` Doug Smythies
2019-12-23 14:07 ` Qais Yousef
2019-12-23 14:40 ` Qais Yousef
2019-12-23 16:34 ` Doug Smythies
2019-12-23 19:10 ` Qais Yousef
2019-12-24 1:16 ` Doug Smythies
2019-12-24 11:08 ` Qais Yousef
2019-12-02 16:34 ` Ionela Voinescu
2019-12-06 11:57 ` Giovanni Gherdovich
2019-12-18 19:34 ` Peter Zijlstra
2019-12-19 20:27 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 2/6] x86,sched: Add support for frequency invariance on SKYLAKE_X Giovanni Gherdovich
2019-12-18 20:06 ` Peter Zijlstra
2019-12-19 20:29 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 3/6] x86,sched: Add support for frequency invariance on XEON_PHI_KNL/KNM Giovanni Gherdovich
2019-12-18 20:22 ` Peter Zijlstra
2019-12-19 20:32 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 4/6] x86,sched: Add support for frequency invariance on ATOM_GOLDMONT* Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 5/6] x86,sched: Add support for frequency invariance on ATOM Giovanni Gherdovich
2019-11-13 16:50 ` Srinivas Pandruvada
2019-11-15 10:34 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 6/6] x86: intel_pstate: handle runtime turbo disablement/enablement in freq. invariance Giovanni Gherdovich
2019-12-18 20:37 ` [PATCH v4 0/6] Add support for frequency invariance for (some) x86 Peter Zijlstra
2019-12-19 20:33 ` Giovanni Gherdovich
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='001d01d5a4f4$d96b21b0$8c416510$@net' \
--to=dsmythies@telus.net \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--cc=ggherdovich@suse.cz \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=qperret@qperret.net \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).