From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
amod.bodas@atheros.com
Subject: Re: [RFC 0/3] mac80211: new API for handling broadcast / multicast on sw scan
Date: Mon, 30 Aug 2010 16:19:09 +0200 [thread overview]
Message-ID: <1283177949.3691.72.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1282979590-31113-1-git-send-email-lrodriguez@atheros.com>
On Sat, 2010-08-28 at 03:13 -0400, Luis R. Rodriguez wrote:
> mac80211's sw scan doesn't play nice with buffered broadcast and
> multicast frames. Since drivers are required to keep track of the DTIM
> count
I said they were required for powersave, not necessarily for scanning.
> this series provides some new basic functionality to let drivers
> help mac80211 make more prudent decisions for sw scan.
I'm not convinced of this. Why does this need to be so complicated?
Also, some of your comments seem like you're confused about being an AP
vs. being associated to one?
What are you actually trying to achieve? It seems mac80211 can, no
matter what the driver is
- wait for DTIM beacons, and the end of mcast traffic, before going off
channel (should be relevant for p2p as well)
- attempt to do better wrt. scheduling between DTIM, by scheduling
closer (but if DTIM period is 1, this may fail)
- subject to the driver advertising guaranteed TX status, it can also
wait for the nullfunc ACK -- you should also implement flush which
will probably improve things by itself for ath9k
The other things in your patch set I don't understand, but those I think
should be done more generically?
johannes
next prev parent reply other threads:[~2010-08-30 14:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 7:13 [RFC 0/3] mac80211: new API for handling broadcast / multicast on sw scan Luis R. Rodriguez
2010-08-28 7:13 ` [RFC 1/3] ath9k: fix regression which disabled ps on ath9k on all cards Luis R. Rodriguez
2010-08-28 7:13 ` [RFC 2/3] mac80211: allow drivers to specify sw scan wait constraints Luis R. Rodriguez
2010-08-29 19:55 ` Luis R. Rodriguez
2010-08-30 7:29 ` Luis R. Rodriguez
2010-08-30 14:17 ` John W. Linville
2010-08-30 15:16 ` Luis R. Rodriguez
2010-08-28 7:13 ` [RFC 3/3] ath9k: implement the " Luis R. Rodriguez
2010-08-30 14:19 ` Johannes Berg [this message]
2010-08-30 15:37 ` [RFC 0/3] mac80211: new API for handling broadcast / multicast on sw scan Luis R. Rodriguez
2010-08-30 15:47 ` Johannes Berg
2010-08-30 18:00 ` Luis R. Rodriguez
2010-08-30 18:10 ` Johannes Berg
2010-08-30 19:20 ` Luis R. Rodriguez
2010-08-31 14:36 ` Johannes Berg
2010-08-31 15:30 ` Luis R. Rodriguez
2010-08-31 15:54 ` Johannes Berg
2010-08-31 16:59 ` Luis R. Rodriguez
2010-08-31 18:12 ` Johannes Berg
2010-09-01 2:14 ` Luis R. Rodriguez
2010-09-01 10:41 ` 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=1283177949.3691.72.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amod.bodas@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).