All of lore.kernel.org
 help / color / mirror / Atom feed
From: David C Niemi <dniemi@verisign.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Luis Alfonso Maeda-Nunez <lm15g10@ecs.soton.ac.uk>,
	cpufreq@vger.kernel.org, rjw@sisk.pl
Subject: Re: Questions about Runtime PM
Date: Mon, 28 Oct 2013 16:19:39 -0400	[thread overview]
Message-ID: <526EC6DB.2060303@verisign.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1310281512460.1246-100000@iolanthe.rowland.org>

On 10/28/13 15:16, Alan Stern wrote:
> On Mon, 28 Oct 2013, Luis Alfonso Maeda-Nunez wrote:
...
> Reading through the documentation of Runtime PM it 
> sends the processor (or any device) to sleep after a period of idleness. 
> In my system, however, as I am running a benchmark (fft from MiBench) in 
> a loop, suddenly the processor is sent to a low power mode (without 
> being idle). I looked at the traces (attached to this email) and it just 
> goes to C1 (I believe it's for ACPI).
> I don't understand how a CPU can go into a low-power mode like C1 
> without being idle.  By definition, when the CPU isn't in C0, it isn't 
> doing any work.
Depends on how you define "CPU" and "idle".

A busy CPU will have a number of cores idle at least for short periods of time while others are busy.

And a busy core typically spend time in C1 while it waits for I/O (unless it is 100% compute-bound for the long haul and there is zero I/O going on, which is kind of unusual).

I expect fft to be pretty compute-bound, but it's hard to keep all cores 100% busy 100% of the time for long.  Or there may just be a bad idle config.  Is this with intel-idle or acpi-idle?

Also, normally a core hops between C0 and C1 extremely rapidly.  It is more meaningful to talk about what percentage of time it spends in each, it is almost impossible to stay in either one continuously.

DCN


  reply	other threads:[~2013-10-28 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EMEW3|116e69362a474a99eb7966986654fb49p9RFXO07lm15g10|ecs.soton.ac.uk|526E83A9.8000703@ecs.soton.ac.uk>
2013-10-28 19:16 ` Questions about Runtime PM Alan Stern
2013-10-28 20:19   ` David C Niemi [this message]
2015-12-22 13:24 questions about runtime pm Ludovic Desroches
2016-01-15 15:01 ` Ludovic Desroches
2016-01-18  2:35   ` Jaehoon Chung

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=526EC6DB.2060303@verisign.com \
    --to=dniemi@verisign.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=lm15g10@ecs.soton.ac.uk \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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.