Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one
From: Johannes Berg <johannes@sipsolutions.net>
Date: 2018-08-29 23:04:14
Possibly related (same subject, not in this thread)
- 2018-08-30 · Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one · Johannes Berg <johannes@sipsolutions.net>
- 2018-08-30 · Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one · Lorenzo Bianconi <hidden>
- 2018-08-30 · Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one · Johannes Berg <johannes@sipsolutions.net>
- 2018-08-30 · Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one · Johannes Berg <johannes@sipsolutions.net>
- 2018-08-30 · Re: [PATCH v2] mac80211: do not aggregate frames if max_frags is set to one · Lorenzo Bianconi <hidden>
On Wed, 2018-08-29 at 21:03 +0200, Lorenzo Bianconi wrote:
Do not try to aggregate packets in a A-MSDU frame and add A-MSDU header on the first packet if max_tx_fragments or max_amsdu_subframes are set to one Signed-off-by: Lorenzo Bianconi <redacted> --- Changes since v1: - rebased on top of mac80211 master branch - removed ieee80211_amsdu_realloc_pad chunk
Don't you still have to account for the changed header length if the second one fails or something? You said you wanted to account for the pad bytes - which now aren't there - but didn't that also take the changed header of the first subframe into account? johannes