All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 9 Jun 2013 23:14:49 +0200	[thread overview]
Message-ID: <20130609211449.GA5517@pd.tnic> (raw)
In-Reply-To: <7661669.NhG4BEI8zO@vostro.rjw.lan>

On Sun, Jun 09, 2013 at 10:58:51PM +0200, Rafael J. Wysocki wrote:
> Can you possibly prepare a graph showing both the execution time
> and energy consumption for several different loop durations in your
> program (let's keep the 5000 us sleep for now), including multiples of
> sampling_rate as well as some other durations?

Judgind by the times in C0 one of the cores spent, this small program
is single-threaded and is a microbenchmark. And you know how optimizing
against a microbenchmark doesn't really make a lot of sense.

I wonder if lmbench or aim9 or whatever would make more sense to try
here...

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-06-09 21:14 UTC|newest]

Thread overview: 48+ 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 12:34 ` 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 [this message]
2013-06-09 22:11               ` Rafael J. Wysocki
2015-02-23 16:42                 ` nitin
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
2013-06-13 22:37                         ` Borislav Petkov
2013-06-14 12:46                         ` Rafael J. Wysocki
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:56 ` Stratos Karafotis
2013-06-06 12:54 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=20130609211449.GA5517@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 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.