public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: pm qos and cpufreq interaction [Was: pm qos infrastructure and interface]
Date: Tue, 23 Oct 2007 20:03:43 +0200	[thread overview]
Message-ID: <20071023180343.GA2624@isilmar.linta.de> (raw)
In-Reply-To: <20071004215139.GA20078@linux.intel.com>

Hi Mark,

On Thu, Oct 04, 2007 at 02:51:39PM -0700, Mark Gross wrote:
> Currently we have {cpu_dma_latency, network_latency, network_throughput}
> as the initial set of pm_qos parameters.

What about cpu_throughput{_min,_max}, as being something considered to be
proportional to the CPU frequency? This way, the cpufreq policy notifiers
might be able to utilize the pm_qos infrastructure; but maybe even also the
userspace interface (at least the min freq/max freq one)... Haven't thought
this through, but maybe you (or someone else) has.

Best,
	Dominik

PS: Each time I've tried to get back into business during the past
months, something got in between -- current issue is my terminally
broken notebook...

  parent reply	other threads:[~2007-10-23 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071004215139.GA20078@linux.intel.com>
2007-10-11  5:17 ` pm qos infrastructure and interface Andrew Morton
     [not found] ` <20071010221704.6e438c71.akpm@linux-foundation.org>
2007-10-11 15:08   ` Mark Gross
2007-10-11 15:38   ` Arjan van de Ven
2007-10-23 18:03 ` Dominik Brodowski [this message]
2007-10-24 21:21   ` pm qos and cpufreq interaction [Was: pm qos infrastructure and interface] Mark Gross
2007-10-25 18:54     ` Dominik Brodowski
2007-10-25 20:53       ` Mark Gross

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=20071023180343.GA2624@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mgross@linux.intel.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