public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Ran Shalit <ranshalit@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-pm@vger.kernel.org
Subject: Re: suspend/resume PM criterion for application
Date: Wed, 10 Sep 2014 13:59:44 -0400	[thread overview]
Message-ID: <17893.1410371984@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 10 Sep 2014 20:26:48 +0300." <CAJ2oMh+xmgC9mfT5QqEmMMek7SOqYE2QLVV6sPvK0CF5+56hDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

On Wed, 10 Sep 2014 20:26:48 +0300, Ran Shalit said:

> What is usually the criterion for PM (power management) suspending
> that application shall use ? Is it according to minimum threshold for
> cpu load (as indication for no process) ?

That will be highly application dependent.  Something that checks your email
in the background may not care at all, as long as it gets network
access every 5 minutes or so, and the entire system can power down for 4 minutes
and 58 seconds as far as it cares.  If it's doing media streaming, it may
insist on having at least one CPU burst per screen refresh, and the CPU can
go to sleep for the rest of the 1/30th of  a second.

> How usually it is performed, i.e.  is it some periodic process, which
> wakes up periodically to check criterion for cpu load ? If so, isn't
> it problematic in PM terms, becuase it mean that the system is resumed
> periodically (as a result of the the periodic timer's interrupt), and
> all devices are resumed ?

No, it can be done on a per-device basis.

'powertop' is a possibly useful tool for playing with this stuff that will
let you look at power management on the fly.

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-09-10 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 17:26 suspend/resume PM criterion for application Ran Shalit
2014-09-10 17:59 ` Valdis.Kletnieks [this message]
2014-09-10 18:23   ` Ran Shalit
2014-09-10 18:39     ` Valdis.Kletnieks
2014-09-10 18:58       ` Ran Shalit
2014-09-10 19:25         ` Valdis.Kletnieks
2014-09-10 19:31           ` Ran Shalit
2014-09-11  5:32           ` AYAN KUMAR HALDER
2014-09-11  9:24             ` Ran Shalit
2014-09-14  6:11               ` Ran Shalit
2014-09-17  3:16                 ` Peter Teoh
2014-09-17  3:32                   ` Peter Teoh

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=17893.1410371984@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ranshalit@gmail.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