From: Kalle Valo <kalle.valo@nokia.com>
To: "Vivek Natarajan" <vivek.natraj@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211 dynamic powersave
Date: Tue, 11 Nov 2008 14:29:14 +0200 [thread overview]
Message-ID: <87k5babg4l.fsf@nokia.com> (raw)
In-Reply-To: <8e92b4100811102018q4a13568l625abf2c59dca253@mail.gmail.com> (ext Vivek Natarajan's message of "Tue\, 11 Nov 2008 09\:48\:23 +0530")
Vivek Natarajan <vivek.natraj@gmail.com> writes:
> Hello Kalle,
Hello Vivek,
> I have a few questions on the PS implementation. Here they are,
>
> 1) I see from your patch that power save is enabled whenever there
> is no Tx for the specified 'timeout' period. Should we also take into
> account the type of power connection( i.e battery or direct ac supply)
> before enabling PS?
That's a policy decision and should be in user space. User space can
enable or disable the dynamic PS as it sees fit based on different
parameters.
> 2) Do you intend to leave the NULL frame formation
[to the driver]
Yes, that was my and Johannes' plan.
> waking up the chip for TIM
What do you mean by this? Sending a beacon interval setting to the chip?
> and modifying sleep/awake time according to DTIM to the driver since
> I did not see this in your TODO list?
I think these should be in mac80211, just haven't thought that far
yet. I'll add it to the TODO list.
> ( I understand from the iwlwifi code that it just sends a request to
> the firmware for sending NULL frame and the firmware takes care of
> the rest. But it may not be so in the case of other vendor drivers.)
Yes, that's how I have understood iwlwifi to work. Currently stlc45xx
is the only hardware which requires the driver to create the null
frames, but if we are more than one hardware I think we need to
considering adding the feature to mac80211 (with a new HW flag, of
course).
> 3) Is the PS-POLL concept(or M frames in N milliseconds concept of Johannes)
>
> dropped after the DNS response timings related discussion that you had
> since it might save some more power in low-traffic conditions?
I have dropped it for now. I try to get a simple implementation
approved first, we can add advanced stuff later.
--
Kalle Valo
next prev parent reply other threads:[~2008-11-11 12:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 15:43 [RFC] mac80211 dynamic powersave Kalle Valo
2008-11-09 15:43 ` [RFC 1/2] mac80211: enable IEEE80211_CONF_PS only when associated Kalle Valo
2008-11-10 9:28 ` Johannes Berg
2008-11-10 9:36 ` Kalle Valo
2008-11-09 15:43 ` [RFC 2/2] mac80211: implement dynamic power save Kalle Valo
2008-11-10 9:36 ` Johannes Berg
2008-11-10 9:49 ` Kalle Valo
2008-11-10 9:53 ` Johannes Berg
2008-11-10 20:14 ` Luis R. Rodriguez
2008-11-11 7:14 ` Kalle Valo
2008-11-11 10:18 ` Vivek Natarajan
2008-11-11 13:09 ` Kalle Valo
2008-11-11 16:40 ` Nick Kossifidis
2008-11-11 4:32 ` [RFC] mac80211 dynamic powersave Vivek Natarajan
2008-11-11 10:38 ` Johannes Berg
2008-11-12 6:17 ` Vivek Natarajan
2008-11-12 17:33 ` Luis R. Rodriguez
[not found] ` <8e92b4100811102018q4a13568l625abf2c59dca253@mail.gmail.com>
2008-11-11 12:29 ` Kalle Valo [this message]
2008-11-11 12:57 ` Johannes Berg
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=87k5babg4l.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vivek.natraj@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;
as well as URLs for NNTP newsgroup(s).