public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Guru Prasad <gurupras@buffalo.edu>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: cpufreq and memory intensive benchmarks
Date: Mon, 05 Aug 2013 14:57:20 +0200	[thread overview]
Message-ID: <4250106.OFInZbRRQq@vostro.rjw.lan> (raw)
In-Reply-To: <CAOh2x==AR1KQO7f8RSztXpU9g2pCyToikmk6GLO0SXfUGTw3dA@mail.gmail.com>

On Monday, August 05, 2013 12:40:13 PM Viresh Kumar wrote:
> Please remember adding cc'd lists/people in your next mail
> 
> On Sat, Aug 3, 2013 at 1:15 AM, Guru Prasad <gurupras@buffalo.edu> wrote:
> > I was recently running some SPEC benchmarks to test the way in which
> > cpufreq module adjusts the CPU frequency for various benchmarks and I
> > noticed that cpufreq always tends to rest at the maximum frequency
> > regardless of the benchmark on ondemand / conservative.
> 
> They will stay there if cpu is busy doing some activity..
> 
> > I then tried to identify memory intensive benchmarks
> > (http://users.elis.ugent.be/~leeckhou/papers/isca12-2.pdf) and upon
> > running milc / libquantum, I noticed that the same trend continued.
> >
> > Does this mean that memory operation latencies are attributed as CPU busy time?
> > Could someone explain the inner workings behind this? What does the
> > CPU *really* do while the load/store is executing? Is it busy-waiting
> > / idle?
> 
> We actually take cpu's busy vs idle time for all calculations here..
> idle time is calculated by the time cpu was running its idle thread..
> i.e. when CPU doesn't have any process to run and is idle..
> 
> But in your case not sure how cpu would behave.. If cpu is doing
> word-by-word copy of some stuff, it would be busy most of the
> time and isn't really running its idle thread. And so would be counted
> as busy I suppose..
> 
> But if some DMA is taking care of copying stuff then it can be idle,
> depending on what else is getting scheduled on it.
> 
> @Rafael: Am I right?

All depends on whether or not the CPU is idle from the scheduler viewpoint,
so basically this is correct.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-08-05 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 19:45 cpufreq and memory intensive benchmarks Guru Prasad
2013-08-05  7:10 ` Viresh Kumar
2013-08-05 12:57   ` Rafael J. Wysocki [this message]

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=4250106.OFInZbRRQq@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=gurupras@buffalo.edu \
    --cc=linux-pm@vger.kernel.org \
    --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