From: Marco Porsch <marco@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>,
kvalo@adurom.com, "Luis R. Rodriguez" <mcgrof@gmail.com>,
Javier Cardona <javier@cozybit.com>
Cc: linux-wireless@vger.kernel.org
Subject: mesh powersave code layout
Date: Tue, 13 Nov 2012 11:06:20 -0800 [thread overview]
Message-ID: <50A29A2C.9080606@cozybit.com> (raw)
Hi,
I had a presentation on mesh powersave during the Barcelona Wireless
summit. In the following discussion Kalle Valo pointed out to me, that
there was interest in generally moving powersave code out of mac80211.
Now I am unsure where to place my mesh PS code before submission.
Currently my code layout for the mesh mode powersave is like this:
mac80211:
-mesh PS mode setting and state logic
-mesh PS mode indication towards neighbors
-neighbor PS mode tracking
-frame buffering
-frame release in Peer Service Periods
-driver configuration
drivers (ath9k, ath9k_htc, ...):
-configuration
-tracking of neighbors' beacon TBTTs
-determining next wakeup TBTT and hardware configuration for wakeup
-awake window after own beacon (software timer)
Javier Cardona recommended changing that and moving all the mesh PS code
to mac80211 for easy maintenance. So (if possible) the idea would be to
create new ieee80211_ops ála:
-void (*radio_sleep) (struct ieee80211_hw *hw, u64 until_tbtt);
-void (*radio_wakeup)(struct ieee80211_hw *hw);
So, where should the parts go, that are currently planned for the
driver? Is there any general preference?
Regards,
Marco
PS:
My code is available on github:
https://github.com/cozybit/open80211s/tree/ft-powersave .
My presentation slides should show up on linuxwireless in the following
days.
next reply other threads:[~2012-11-13 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 19:06 Marco Porsch [this message]
2012-11-14 9:29 ` mesh powersave code layout 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=50A29A2C.9080606@cozybit.com \
--to=marco@cozybit.com \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).