From: Marco Porsch <marco.porsch@etit.tu-chemnitz.de>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, henry@logout.com,
"greenmesh@lists.osll.spb.ru" <greenmesh@lists.osll.spb.ru>
Subject: Re: [ath9k] mesh powersave hardware sleep + wakeup
Date: Fri, 16 Mar 2012 23:09:53 +0100 [thread overview]
Message-ID: <4F63BA31.1080608@etit.tu-chemnitz.de> (raw)
In-Reply-To: <20120316204547.GG18861@tux>
On 03/16/12 21:45, Luis R. Rodriguez wrote:
> On Fri, Mar 16, 2012 at 10:42:02AM +0100, Marco Porsch wrote:
>> Hi,
>>
>> I am trying to implement the IEEE 802.11s power save schemes in mac80211.
>> In 11s it is defined that power save STA doze AND send beacons AND
>> wake up periodically for multiple neighbors beacons.
>>
>> Is this actually possible with current hardware/drivers (especially ath9k)?
[ ... ]
> I don't have time to review this but it sounds correct that the part
> you want to focus on is introducing a wake up mechanism when you
> need to initiate radiation for your own beacons. I think right now
> we simply disable PS in mac80211 completely if we have a mode of
> operation that require beconing.
Actually the whole power save code is only written specifically for
managed mode.
E.g. for ad-hoc, you wouldn't suspend the radio, since the MAC schemes
that must deal with the resulting deafness issues are not implemented in
mac80211. (That would be frame buffering + release in ATIM window, ...)
Concerning mesh, I already have a hackish - but mostly working - PS
frame buffering and release.
But, what is power save without actually saving power?
Problem: I don't have a reference how to suspend/wake the radio between
sending beacons.
That's why I hoped you can tell me, if - at least in theory - the
hardware/ath9k even allows this.
> Your challenge is to lift that and
> deal with the issues there and all the possible combinations. You
> can help with this
>
> This should help you:
>
> http://wireless.kernel.org/en/users/Documentation/Power-consumption
Thanks, the numbers are nice I can use them for analytical estimation or
simulation.
> For now you can focus on only allowing through Mesh devices and
> the combinations of it but I suspect that some of the work you do
> may also help with addressing P2P powersave.
Correct. When this is implemented, it is easy to port this to ad-hoc.
Because mesh is definitively more complex, but similar.
Regards,
Marco
next prev parent reply other threads:[~2012-03-16 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 9:42 [ath9k] mesh powersave hardware sleep + wakeup Marco Porsch
2012-03-16 20:45 ` Luis R. Rodriguez
2012-03-16 22:09 ` Marco Porsch [this message]
2012-04-11 11:00 ` [Greenmesh] " Marco Porsch
2012-04-12 4:05 ` Johannes Berg
2012-04-12 7:41 ` Marco Porsch
2012-04-18 2:02 ` Johannes Berg
2012-04-18 14:56 ` Javier Cardona
2012-04-18 15:05 ` Johannes Berg
2012-04-18 15:16 ` Javier Cardona
2012-04-19 2:41 ` Yeoh Chun-Yeow
2012-04-19 2:51 ` Javier Cardona
2012-04-27 15:53 ` Marco Porsch
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=4F63BA31.1080608@etit.tu-chemnitz.de \
--to=marco.porsch@etit.tu-chemnitz.de \
--cc=greenmesh@lists.osll.spb.ru \
--cc=henry@logout.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rodrigue@qca.qualcomm.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).