From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stratos Karafotis <stratosk@semaphore.gr>,
Borislav Petkov <bp@suse.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-pm@vger.kernel.org, cpufreq@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] cpufreq: ondemand: Change the calculation of target frequency
Date: Fri, 14 Jun 2013 00:37:41 +0200 [thread overview]
Message-ID: <20130613223740.GE32112@pd.tnic> (raw)
In-Reply-To: <1645236.hTWQPUhyIx@vostro.rjw.lan>
On Fri, Jun 14, 2013 at 12:15:36AM +0200, Rafael J. Wysocki wrote:
> On Thursday, June 13, 2013 11:40:08 PM Borislav Petkov wrote:
[ … ]
> > Not bad. However, exec_test and fork_test are kinda unexpected with such
> > a high improvement percentage. Happen to have an explanation?
> >
> > FWIW, if we don't find any serious perf/power regressions with
> > this patch, I'd say it is worth applying even solely for the code
> > simplification it brings.
>
> May I take this as an ACK? ;-)
>
> Well, that's my opinion too, actually.
I know - you told me and I like that aspect :-). And from the test
results so far, the code simplification is maybe the most persuasive
one. The slight improvements in perf/power are then the cherry on top.
Although, I'm not sure we're exhaustive with the benchmarks and we
should maybe run a couple more. Although, judging by the results,
generally no serious outliers should be expected (except exec_test and
fork_test funsies above), which are actually positive outliers.
Judging by the code change, the only worry we should have, AFAIU, is
any raise in power consumption due to spending longer periods in the
intermediary P-states now and not going straight to the lowest P-state.
But this compensates with improvement in runtime of the workloads.
Hmm, I dunno - I'm just thinking out loud here...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-06-13 22:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 12:34 [PATCH v3 1/3] cpufreq: ondemand: Change the calculation of target frequency Stratos Karafotis
2013-06-08 14:05 ` Rafael J. Wysocki
2013-06-08 20:31 ` Stratos Karafotis
2013-06-08 22:18 ` Rafael J. Wysocki
2013-06-09 16:26 ` Borislav Petkov
2013-06-09 18:08 ` Stratos Karafotis
2013-06-09 20:58 ` Rafael J. Wysocki
2013-06-09 21:14 ` Borislav Petkov
2013-06-09 22:11 ` Rafael J. Wysocki
2013-06-10 21:57 ` Stratos Karafotis
2013-06-10 23:24 ` Rafael J. Wysocki
2013-06-13 21:22 ` Stratos Karafotis
2013-06-13 21:40 ` Borislav Petkov
2013-06-13 22:04 ` Stratos Karafotis
2013-06-13 22:38 ` Borislav Petkov
2013-06-13 22:15 ` Rafael J. Wysocki
2013-06-13 22:37 ` Borislav Petkov [this message]
2013-06-14 12:46 ` Rafael J. Wysocki
2013-06-14 12:44 ` Borislav Petkov
2013-06-14 12:55 ` Rafael J. Wysocki
2013-06-14 15:53 ` Stratos Karafotis
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 12:56 Stratos Karafotis
2013-06-06 12:54 Stratos Karafotis
2013-06-06 13:15 ` Borislav Petkov
2013-06-05 16:01 Stratos Karafotis
2013-06-05 16:17 ` Borislav Petkov
2013-06-05 16:58 ` David C Niemi
2013-06-06 9:55 ` Borislav Petkov
2013-06-06 9:57 ` Viresh Kumar
2013-06-06 13:50 ` David C Niemi
2013-06-05 17:13 ` Stratos Karafotis
2013-06-05 20:35 ` Rafael J. Wysocki
2013-06-06 10:01 ` Borislav Petkov
2013-06-06 10:10 ` Viresh Kumar
2013-06-06 12:10 ` Borislav Petkov
2013-06-06 16:46 ` Stratos Karafotis
2013-06-06 17:11 ` Borislav Petkov
2013-06-06 17:32 ` Stratos Karafotis
2013-06-07 19:14 ` Stratos Karafotis
2013-06-07 20:57 ` Rafael J. Wysocki
2013-06-08 9:56 ` Stratos Karafotis
2013-06-08 11:18 ` Rafael J. Wysocki
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=20130613223740.GE32112@pd.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=stratosk@semaphore.gr \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@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