From: Viresh Kumar <viresh.kumar@linaro.org>
To: Andreas Herrmann <aherrmann@suse.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Stratos Karafotis <stratosk@semaphore.gr>,
Thomas Renninger <trenn@suse.com>
Subject: Re: [PATCH v2 1/2] cpufreq/ondemand: Introduce op to customize mapping of load to frequency
Date: Wed, 5 Oct 2016 09:31:18 +0530 [thread overview]
Message-ID: <20161005040118.GJ4664@vireshk-i7> (raw)
In-Reply-To: <20160923170256.GB9786@suselix.suse.de>
On 23-09-16, 19:02, Andreas Herrmann wrote:
> Introduce op for ondemand governor that is used to map load to
> frequency. It allows a cpufreq driver to provide a specific mapping
> function if the generic function is not optimal for the driver.
>
> Performance results (kernel compile with different number of jobs)
> based on 4.8.0-rc7 (with and w/o my patches on top) from
> an HP ProLiant DL580 Gen8 system using pcc-cpufreq:
> - Intel(R) Xeon(R) CPU E7-4890 v2 @ 2.80GHz
> - 60 CPUs, 128GB RAM
>
> vanilla generic_map_load_to_freq function
> # of jobs user sys elapsed % CPU user sys elapsed % CPU
> 2 445.44 110.51 272.99 203.00 445.56 111.22 273.35 203.00
> 4 444.41 126.20 142.81 399.00 445.61 126.10 143.12 399.00
> 8 483.04 150.58 82.19 770.40 483.51 150.84 82.17 771.40
> 16 626.81 185.01 55.00 1475.40 628.01 185.54 55.02 1477.80
> 32 816.72 204.39 37.26 2740.00 818.58 205.51 37.02 2765.40
> 64 406.59 51.12 14.04 3257.80 406.22 51.84 13.84 3308.80
> 120 413.00 48.39 14.36 3211.20 413.61 49.06 14.54 3181.00
>
> Similar tests on another system using acpi_cpufreq didn't show
> significant performance differences between these two kernel versions.
>
> Link: https://marc.info/?i=20160819121814.GA17296%40suselix.suse.de
> Signed-off-by: Andreas Herrmann <aherrmann@suse.com>
> ---
> drivers/cpufreq/cpufreq_governor.h | 5 +++++
> drivers/cpufreq/cpufreq_ondemand.c | 35 ++++++++++++++++++++++++++++++-----
> 2 files changed, 35 insertions(+), 5 deletions(-)
NAK.
If we are absolutely required to hack it in some way, then I would
prefer your first patchset as the noise was limited to only your
driver.
We aren't going to provide such operations from the governors, sorry.
--
viresh
next prev parent reply other threads:[~2016-10-05 4:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 12:18 [PATCH 0/1] cpufreq: pcc-cpufreq: Re-introduce deadband effect to reduce number of frequency changes Andreas Herrmann
2016-08-19 12:21 ` [PATCH 1/1] " Andreas Herrmann
2016-08-29 6:01 ` Viresh Kumar
2016-09-01 13:21 ` Andreas Herrmann
2016-09-07 5:02 ` Viresh Kumar
2016-09-13 10:53 ` Andreas Herrmann
2016-09-14 14:56 ` Andreas Herrmann
2016-10-05 5:17 ` Viresh Kumar
2016-10-11 6:28 ` Andreas Herrmann
2016-09-16 9:47 ` Andreas Herrmann
2016-09-16 18:48 ` Stratos Karafotis
[not found] ` <CADmjqpNE9f7fzQjWsHKB4wEjLq-4ZvQpaC314OcLdQ-i_TAABg@mail.gmail.com>
2016-09-19 16:16 ` Andreas Herrmann
2016-09-19 19:39 ` Stratos Karafotis
2016-09-22 17:54 ` Andreas Herrmann
2016-10-05 5:21 ` Viresh Kumar
2016-08-19 12:40 ` [PATCH 0/1] " Andreas Herrmann
2016-09-23 16:56 ` [PATCH v2 0/2] " Andreas Herrmann
2016-09-23 17:02 ` [PATCH v2 1/2] cpufreq/ondemand: Introduce op to customize mapping of load to frequency Andreas Herrmann
2016-10-05 4:01 ` Viresh Kumar [this message]
2016-10-11 6:30 ` Andreas Herrmann
2016-09-23 17:07 ` [PATCH v2 2/2] cpufreq/pcc-cpufreq: Make use of map_load_to_freq op Andreas Herrmann
2016-09-26 9:05 ` [PATCH v3 " Andreas Herrmann
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=20161005040118.GJ4664@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=aherrmann@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stratosk@semaphore.gr \
--cc=trenn@suse.com \
/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