From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 0/6] RFC: CPU frequency min/max as PM QoS params
Date: Thu, 12 Jan 2012 00:15:55 +0100 [thread overview]
Message-ID: <201201120015.55740.rjw@sisk.pl> (raw)
In-Reply-To: <87vcoid7j5.fsf@amiettinen-lnx.nvidia.com>
On Wednesday, January 11, 2012, Antti P Miettinen wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> > On Monday, January 09, 2012, Antti P Miettinen wrote:
> >> Hmm.. congestion is an issue for latency requests as well.
> >
> > I'm not sure what you mean. Care to elaborate?
> >
> > Rafael
>
> Well, I was just thinking that latencies can get hurt by system load
> just like throughput can suffer from load.
The idea with latencies is different. Latency constraints specify how
much time a given resource may be unavailable (due to power management).
So, when putting the resource into a low-power state we only need to
consider the minimum of those.
> By blocking sleep states we can address "system level latency" or "best case
> latency" but as far as I can see PM QoS does not address "worst case
> latency".
I'm not sure what you mean by "worst case latency".
Thanks,
Rafael
next prev parent reply other threads:[~2012-01-11 23:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 0:36 [PATCH 0/6] RFC: CPU frequency min/max as PM QoS params Antti P Miettinen
2012-01-06 0:36 ` [PATCH 1/6] PM QoS: Simplify PM QoS expansion/merge Antti P Miettinen
2012-01-06 15:24 ` mark gross
2012-01-08 23:03 ` Rafael J. Wysocki
2012-01-06 0:36 ` [PATCH 2/6] PM QoS: Add CPU frequency min/max as PM QoS params Antti P Miettinen
2012-01-06 15:30 ` mark gross
2012-01-06 19:32 ` Antti P Miettinen
2012-01-07 3:47 ` mark gross
2012-01-07 8:54 ` Antti P Miettinen
2012-01-06 0:36 ` [PATCH 3/6] cpufreq: Export user_policy min/max Antti P Miettinen
2012-01-06 15:33 ` mark gross
2012-01-06 19:29 ` Antti P Miettinen
2012-01-07 3:53 ` mark gross
2012-01-07 8:47 ` Antti P Miettinen
2012-01-09 14:18 ` [linux-pm] " mark gross
2012-01-09 14:18 ` mark gross
2012-01-06 0:36 ` [PATCH 4/6] cpufreq: Preserve sysfs min/max request Antti P Miettinen
2012-01-06 0:36 ` [PATCH 5/6] cpufreq: Enforce PM QoS min/max limits Antti P Miettinen
2012-01-06 15:38 ` mark gross
2012-01-06 0:36 ` [PATCH 6/6] input: CPU frequency booster Antti P Miettinen
2012-01-06 15:40 ` mark gross
2012-01-06 15:18 ` [PATCH 0/6] RFC: CPU frequency min/max as PM QoS params mark gross
2012-01-06 15:46 ` mark gross
2012-01-06 19:38 ` Antti P Miettinen
2012-01-07 2:57 ` mark gross
2012-01-06 18:27 ` mark gross
2012-01-08 22:59 ` Rafael J. Wysocki
2012-01-09 14:23 ` mark gross
2012-01-09 21:27 ` Rafael J. Wysocki
2012-01-09 21:57 ` Antti P Miettinen
2012-01-10 20:44 ` Rafael J. Wysocki
2012-01-11 7:26 ` Antti P Miettinen
2012-01-11 23:15 ` Rafael J. Wysocki [this message]
2012-01-12 8:37 ` Antti P Miettinen
2012-01-12 23:55 ` Rafael J. Wysocki
2012-01-10 4:50 ` mark gross
2012-01-10 20:46 ` Rafael J. Wysocki
2012-01-10 21:02 ` Jean Pihet
2012-01-11 7:32 ` Antti P Miettinen
2012-01-11 23:00 ` Rafael J. Wysocki
2012-01-12 8:43 ` Antti P Miettinen
2012-01-13 4:37 ` mark gross
2012-01-12 3:06 ` mark gross
2012-01-12 23:52 ` Rafael J. Wysocki
2012-01-12 3:01 ` mark gross
-- strict thread matches above, loose matches on Subject: below --
2012-01-06 10:03 Antti P Miettinen
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=201201120015.55740.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=amiettinen@nvidia.com \
--cc=linux-pm@lists.linux-foundation.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.