From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Dan Williams <dcbw@redhat.com>,
"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kalle.valo@iki.fi>, Matthew Garrett <mjg@redhat.com>
Subject: Re: wireless powersaving (in NM?)
Date: Wed, 25 Mar 2009 11:45:25 +0100 [thread overview]
Message-ID: <1237977925.4320.138.camel@johannes.local> (raw)
In-Reply-To: <1237890734.4740.7.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On Tue, 2009-03-24 at 11:32 +0100, Marcel Holtmann wrote:
> I prefer that we not export this over WEXT at all and only via nl80211
> so we get async notification if some one changes it. We should extend
> wpa_supplicant with an option to set power saving on/off/default and
> then make sure it gets exported via its CLI or D-Bus. So if Network
> Manger or ConnMan cares to change these values they can.
>
> However personally I think the need for enabling or disabling power
> savings is not really useful except for testing purposes. In a real life
> deployed system it should be enabled all the time. Broken drivers or
> hardware that is limited can disable it on kernel level, but for
> userspace we only need this for debugging.
Kalle makes a point about broken APs, which I personally haven't run
into but I'm sure exist -- and I see no way to automatically detect
that. Therefore, it seems necessary to allow overriding this even for
non-debugging purposes.
I have no problem with just changing the default to be enabled though,
but that requires some work to turn off automatically for most virtual
interface combinations. As I said before -- this needs to be fairly
conservative and only when applications register their requirements can
we go to lower power states with higher latency.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-25 10:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:39 wireless powersaving (in NM?) Johannes Berg
2009-03-24 10:32 ` Marcel Holtmann
2009-03-25 10:45 ` Johannes Berg [this message]
2009-03-24 13:47 ` John W. Linville
2009-03-24 13:53 ` Johannes Berg
2009-03-24 14:47 ` Guy, Wey-Yi W
2009-03-24 15:03 ` Kalle Valo
2009-03-24 14:17 ` Kalle Valo
2009-03-25 10:57 ` Johannes Berg
2009-03-25 19:53 ` Kalle Valo
2009-03-25 20:06 ` Johannes Berg
2009-03-25 20:09 ` Johannes Berg
2009-03-25 20:22 ` Kalle Valo
2009-03-24 15:59 ` Dan Williams
2009-03-25 11:04 ` Johannes Berg
2009-03-25 15:31 ` Dan Williams
2009-03-25 15:48 ` Johannes Berg
2009-03-26 8:00 ` Luis R. Rodriguez
2009-03-26 8:11 ` Johannes Berg
2009-03-26 8:39 ` Luis R. Rodriguez
2009-03-26 8:54 ` Johannes Berg
2009-03-26 9:01 ` Luis R. Rodriguez
2009-03-26 14:29 ` Georgy Berdyshev
2009-03-26 8:19 ` Kalle Valo
2009-03-26 8:40 ` Luis R. Rodriguez
2009-03-31 16:28 ` Johannes Berg
2009-04-01 11:04 ` more thoughts on power saving (was: wireless powersaving (in NM?)) Johannes Berg
2009-04-01 11:12 ` Kalle Valo
2009-04-01 14:29 ` Guy, Wey-Yi W
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=1237977925.4320.138.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mjg@redhat.com \
--cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).