From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "Sean Patrick Santos" <quantheory@gmail.com>,
linux-wireless@vger.kernel.org, nbd@openwrt.org,
helmut.schaa@googlemail.com, mar.kolya@gmail.com,
"Per-Erik Westerberg" <per-erik.westerberg@bredband.net>,
"Mikołaj Kuligowski" <mikolaj.q@wp.pl>
Subject: Re: [RFC v2] mac80211: follow 802.11-2007 11.5.3 Error recovery upon HT BA failure
Date: Sat, 09 Jun 2012 14:28:12 +0200 [thread overview]
Message-ID: <1339244892.5763.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201206091414.41940.chunkeey@googlemail.com> (sfid-20120609_141447_009272_4C308145)
On Sat, 2012-06-09 at 14:14 +0200, Christian Lamparter wrote:
> yeah, I should. But 802.11-2012 is not yet available for
> free like the old 802.11-2007 through IEEE 802 Get.
Hah, ok. I guess I can fix the references when I apply it.
> > > This patch was only compile-tested and the design has
> > > some rather big problems:
> >
> > Maybe then we should just revert Nikolay's patch?
> (I was referring to this RFC patch and not his patch)
Oh.
> I don't think we can/should revert it, just change it
> a bit so the timeout reset is triggered by a received
> BA from the peer.
Makes sense I guess.
> > > - The spec says we should test for BlockAcks, however
> > > that is not feasible because it is a control frame
> > > (so FIF_CONTROL might filter it on some hardware).
> >
> > In some way, all devices are going to have to report these
> > frames. Maybe not as the frame itself, but as some other
> > notification, to allow cleaning up the TX queues
> > accordingly, I think? There's a BA notification in iwlwifi
> > for example.
> Alright, I guess this means that we probably need a new HW
> feature flag like:
> IEEE80211_HW_REPORTS_BA_NOTIFICATION
> for hardware/firmware which filter BA frames, but have a BA
> notification trap. And every other driver need to pass BA
> to the stack where a new rx handler will update the last_tx
> accordingly.
But that notification trap would also have to call some function in the
stack, and the drivers that don't have it (or don't implement it yet)
need something more like this patch?
I haven't actually looked into the specifics yet at all, will do that on
Monday.
johannes
next prev parent reply other threads:[~2012-06-09 12:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 6:53 Sean Patrick Santos
2012-06-07 13:18 ` carl9170 issue Christian Lamparter
2012-06-07 19:31 ` Sean Patrick Santos
2012-06-08 7:57 ` Sean Patrick Santos
2012-06-09 0:18 ` BA session issue due to old BARs? Christian Lamparter
2012-06-09 1:11 ` [RFC] mac80211: follow 802.11-2007 11.5.3 Error recovery upon HT BA failure Christian Lamparter
2012-06-09 7:59 ` Johannes Berg
2012-06-09 12:14 ` [RFC v2] " Christian Lamparter
2012-06-09 12:28 ` Johannes Berg [this message]
2012-06-09 14:01 ` [RFC v3] " Christian Lamparter
2012-06-10 5:13 ` Emmanuel Grumbach
2012-06-10 12:20 ` Christian Lamparter
2012-06-10 18:55 ` Emmanuel Grumbach
2012-06-09 12:20 ` BA session issue due to old BARs? Helmut Schaa
2012-06-09 14:23 ` Christian Lamparter
2012-06-09 14:55 ` Felix Fietkau
2012-06-09 17:40 ` Christian Lamparter
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=1339244892.5763.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mar.kolya@gmail.com \
--cc=mikolaj.q@wp.pl \
--cc=nbd@openwrt.org \
--cc=per-erik.westerberg@bredband.net \
--cc=quantheory@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).