From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Jouni Malinen <j@w1.fi>
Subject: [RFC 0/3] fix the aMPDU reorder placement
Date: Mon, 16 Nov 2009 15:21:34 +0100 [thread overview]
Message-ID: <20091116142134.288122270@sipsolutions.net> (raw)
Our code has a comment about where the reordering
should happen, and why it doesn't hurt being where
it currently is.
However, this code needs to use sta_info_get()
without knowing which virtual interface is the one
we're processing the frames for, which is getting
in my way.
Rather than trying to find the virtual interface
by the DA, I decided to put the reorder code at the
right place instead because then the station pointer
is already known (so we even save a lookup).
Please test! Especially against APs that are prone
to hitting the timeout.
johannes
next reply other threads:[~2009-11-16 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 14:21 Johannes Berg [this message]
2009-11-16 14:21 ` [RFC 1/3] mac80211: move cmntr flag out of rx flags Johannes Berg
2009-11-16 14:21 ` [RFC 2/3] mac80211: move aMPDU RX reorder code Johannes Berg
2009-11-16 14:21 ` [RFC 3/3] mac80211: correctly place " 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=20091116142134.288122270@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
/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).