From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, johannes@sipsolutions.net
Subject: Re: [PATCH] mac80211: make ieee80211_send_bar available for drivers
Date: Sat, 20 Aug 2011 20:26:02 +0200 [thread overview]
Message-ID: <4E4FFC3A.8070706@openwrt.org> (raw)
In-Reply-To: <1313848435-45702-1-git-send-email-nbd@openwrt.org>
On 2011-08-20 3:53 PM, Felix Fietkau wrote:
> To properly maintain the peer's block ack window, the driver needs to be
> able to control the new starting sequence number that is sent along with
> the BlockAckReq frame.
>
> Signed-off-by: Felix Fietkau<nbd@openwrt.org>
> ---
> turns out that I will need this change in mac80211 anyway to properly
> handle a few corner cases wrt. aggregation and off-channel activity.
>
> When ath9k goes off-channel it may need to drop some packets that are
> still part of the BAW, but at that point in time it would be a very
> bad idea to try to send BAR frames. Instead I want to send the BAR
> after switching back to the primary channel as a kind of barrier before
> sending more packets.
Johannes, do you think it would make the driver API better if instead of
exporting this function, I add an ieee80211_bar_get function (similar to
ieee80211_nullfunc_get or ieee80211_probereq_get) to avoid concerns over
the missing _ni variant or the weird callchain from the driver back into
the tx function?
- Felix
next prev parent reply other threads:[~2011-08-20 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 13:53 [PATCH] mac80211: make ieee80211_send_bar available for drivers Felix Fietkau
2011-08-20 18:26 ` Felix Fietkau [this message]
2011-08-29 13:26 ` 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=4E4FFC3A.8070706@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).