From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org, m.sujith@gmail.com, tomasw@gmail.com
Subject: Re: [RFC/RFT 06/11] mac80211: document TX aggregation (and small cleanup)
Date: Fri, 30 Jan 2009 09:08:28 +0100 [thread overview]
Message-ID: <1233302908.4161.8.camel@johannes.local> (raw)
In-Reply-To: <20090129215152.GA27253@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
On Thu, 2009-01-29 at 23:51 +0200, Jouni Malinen wrote:
> On Thu, Jan 29, 2009 at 01:54:56AM +0100, Johannes Berg wrote:
>
> > + * DOC: TX aggregation
>
> > + * When TX aggregation is started by some subsystem (usually the rate control
> > + * control algorithm would be appropriate) by calling the
> > + * ieee80211_start_tx_ba_session() function, the driver will be notified via
> > + * its @ampdu_action function, with the %IEEE80211_AMPDU_TX_START action.
>
> Does rate control (btw, remove the duplicated "control" from the text)
Oops, thanks.
> algorithm have knowledge of whether PTK has already been configured?
> There is going to be a somewhat unfortunate timing issue with trying to
> set up aggregation before 4-way handshake has been completed if 802.11w
> is used (Action frames are dropped before the keys are set). Something
> in the system (either the request or mac80211's action on the request)
> would need to be delayed until the keys are in place in such a case.
Interesting issue, something I wasn't aware of. Yes, we'd need to delay
it in that case, not that it makes sense to set up aggregation that
early -- who knows it's going to be used? My AP at least will disable
your session if you're fairly idle (I guess to save reorder buffer
resources). We can simply delay it in mac80211, or we can just return
-EAGAIN. For iwl-agn-rs it wouldn't matter, it tries to enable
aggregation repeatedly even while it's already enabled =)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-01-30 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 0:54 [RFC/RFT 00/11] mac80211 HT code improvements/bug fixes Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 01/11] mac80211: remove stray aggregation debugfs definition Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 02/11] mac80211: fix RX aggregation timeouts Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 03/11] mac80211: restructure HT code Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 04/11] mac80211: restrict aggregation to supported interface modes Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 05/11] mac80211: hardware should not deny going back to legacy Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 06/11] mac80211: document TX aggregation (and small cleanup) Johannes Berg
2009-01-29 21:51 ` Jouni Malinen
2009-01-30 8:08 ` Johannes Berg [this message]
2009-01-29 0:54 ` [RFC/RFT 07/11] mac80211: fix race in TX aggregation Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 08/11] mac80211: fix aggregation timer lockups Johannes Berg
2009-01-29 0:54 ` [RFC/RFT 09/11] mac80211: clean up BA session teardown Johannes Berg
2009-01-29 0:55 ` [RFC/RFT 10/11] mac80211: RX aggregation: clean up stop session Johannes Berg
2009-01-29 0:55 ` [RFC/RFT 11/11] mac80211: further cleanups to stopping BA sessions 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=1233302908.4161.8.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@gmail.com \
--cc=tomasw@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).