From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5 3/3] mac80211: implement dynamic power save
Date: Sun, 28 Dec 2008 13:17:45 +0000 [thread overview]
Message-ID: <20081228131745.GA9554@srcf.ucam.org> (raw)
In-Reply-To: <87sko8mohv.fsf@nokia.com>
On Sun, Dec 28, 2008 at 03:13:32PM +0200, Kalle Valo wrote:
> Matthew Garrett <mjg59@srcf.ucam.org> writes:
> > It allows userspace applications to register their latency requirements.
> > There's a notifier chain that then allows drivers (or subsystems) to be
> > notified of the current requirements, the idea being that they can then
> > limit their deepest power saving mode to one that still satisfies the
> > userspace constraints.
>
> Do these constrainsts also include network latency? Do you have any
> suggestions for bedtime reading? :)
Yes, one of the chains is network latency. It's documented in
Documentation/power/pm_qos_interface.txt.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2008-12-28 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:16 [PATCH v5 0/3] mac80211 dynamic power save Kalle Valo
2008-12-18 21:16 ` [PATCH v5 1/3] mac80211: enable IEEE80211_CONF_PS only when associated Kalle Valo
2008-12-18 21:21 ` Johannes Berg
2008-12-18 21:24 ` Kalle Valo
2008-12-18 21:17 ` [PATCH v5 2/3] mac80211: track master queue status Kalle Valo
2008-12-18 21:23 ` Johannes Berg
2008-12-18 21:17 ` [PATCH v5 3/3] mac80211: implement dynamic power save Kalle Valo
2008-12-18 21:25 ` Johannes Berg
2008-12-24 13:24 ` Matthew Garrett
2008-12-28 12:59 ` Kalle Valo
2008-12-28 13:06 ` Matthew Garrett
2008-12-28 13:13 ` Kalle Valo
2008-12-28 13:17 ` Matthew Garrett [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=20081228131745.GA9554@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).