From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@suse.de>, Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
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>,
Vincent Guittot <vincent.guittot@linaro.org>,
Quentin Perret <qperret@qperret.net>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Doug Smythies <dsmythies@telus.net>
Subject: Re: [PATCH v4 5/6] x86,sched: Add support for frequency invariance on ATOM
Date: Fri, 15 Nov 2019 11:34:21 +0100 [thread overview]
Message-ID: <1573814061.28635.2.camel@suse.cz> (raw)
In-Reply-To: <64baa18f7cd6066cc50360928d77504c1b68773e.camel@linux.intel.com>
On Wed, 2019-11-13 at 08:50 -0800, Srinivas Pandruvada wrote:
> On Wed, 2019-11-13 at 13:46 +0100, Giovanni Gherdovich wrote:
> > The scheduler needs the ratio freq_curr/freq_max for frequency-
> > invariant
> > accounting. On all ATOM CPUs prior to Goldmont, set freq_max to the
> > 1-core
> > turbo ratio.
> >
> > We intended to perform tests validating that this patch doesn't
> > regress in
> > terms of energy efficiency, given that this is the primary concern on
> > Atom
> > processors. Alas, we found out that turbostat doesn't support reading
> > RAPL
> > interfaces on our test machine (Airmont), and we don't have external
> > equipment
> > to measure power consumption; all we have is the performance results
> > of the
> > benchmarks we ran.
> >
>
> I can run some benchmarks on this.
>
That'd be appreciated, thank you Srinivas.
Giovanni
next prev parent reply other threads:[~2019-11-15 10:28 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
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 [this message]
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=1573814061.28635.2.camel@suse.cz \
--to=ggherdovich@suse.cz \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--cc=dsmythies@telus.net \
--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 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.