From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@nbd.name>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: support A-MSDU in fast-rx
Date: Tue, 27 Feb 2018 11:58:59 +0100 [thread overview]
Message-ID: <1519729139.4086.9.camel@sipsolutions.net> (raw)
In-Reply-To: <20180227075219.2049-1-nbd@nbd.name>
On Tue, 2018-02-27 at 08:52 +0100, Felix Fietkau wrote:
>
> if (fast_rx->key && !(status->flag & RX_FLAG_IV_STRIPPED)) {
> + if (status->rx_flags & IEEE80211_RX_AMSDU)
> + return false;
This seemed really odd to me.
> /* GCMP header length is the same */
> snap_offs += IEEE80211_CCMP_HDR_LEN;
I understand now though - the problem is that snap_offs isn't used in
__ieee80211_rx_h_amsdu(), and thus we can't do the necessary
adjustments.
I think though that perhaps it'd be better to teach
__ieee80211_rx_h_amsdu() about snap_offs, because assuming in the AMSDU
decap code that snap_offs is more-or-less constant will just make the
dependencies much harder to understand.
Better teach __ieee80211_rx_h_amsdu() about snap_offs, and make the
assumption on the constant in ieee80211_rx_h_amsdu()?
> + if (status->rx_flags & IEEE80211_RX_AMSDU) {
> + res = __ieee80211_rx_h_amsdu(rx);
> + if (res != RX_QUEUED)
> + goto drop;
> +
> + return true;
> + }
Btw, you also don't need the "res" variable, much less at function
scope; this block would do if at all, but also it should probably use
the right enum type or just be removed.
johannes
prev parent reply other threads:[~2018-02-27 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 7:52 [PATCH] mac80211: support A-MSDU in fast-rx Felix Fietkau
2018-02-27 10:58 ` Johannes Berg [this message]
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=1519729139.4086.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).