From: Peter Seiderer <ps.report@gmx.net>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC v2] mac80211: minstrel_ht: do not set RTS/CTS flag for fallback rates
Date: Fri, 26 Nov 2021 15:25:58 +0100 [thread overview]
Message-ID: <20211126152558.4d9fbce3@gmx.net> (raw)
In-Reply-To: <e098a58a-8ec0-f90d-dbc9-7b621e31d051@nbd.name>
Hello Felix,
On Fri, 26 Nov 2021 13:47:07 +0100, Felix Fietkau <nbd@nbd.name> wrote:
> On 2021-11-16 22:28, Peter Seiderer wrote:
> > Despite the 'RTS thr:off' setting a wireshark trace of IBSS
> > traffic with HT40 mode enabled between two ath9k cards revealed
> > some RTS/CTS traffic.
> >
> > Debug and code analysis showed that most places setting
> > IEEE80211_TX_RC_USE_RTS_CTS respect the RTS strategy by
> > evaluating rts_threshold, e.g. net/mac80211/tx.c:
> >
> > 698 /* set up RTS protection if desired */
> > 699 if (len > tx->local->hw.wiphy->rts_threshold) {
> > 700 txrc.rts = true;
> > 701 }
> > 702
> > 703 info->control.use_rts = txrc.rts;
> >
> > or drivers/net/wireless/ath/ath9k/xmit.c
> >
> > 1238 /*
> > 1239 * Handle RTS threshold for unaggregated HT frames.
> > 1240 */
> > 1241 if (bf_isampdu(bf) && !bf_isaggr(bf) &&
> > 1242 (rates[i].flags & IEEE80211_TX_RC_MCS) &&
> > 1243 unlikely(rts_thresh != (u32) -1)) {
> > 1244 if (!rts_thresh || (len > rts_thresh))
> > 1245 rts = true;
> > 1246 }
> >
> > The only place setting IEEE80211_TX_RC_USE_RTS_CTS unconditionally
> > was found in net/mac80211/rc80211_minstrel_ht.c.
> >
> > As the use_rts value is only calculated after hitting the minstrel_ht code
> > preferre to not set IEEE80211_TX_RC_USE_RTS_CTS (and overruling the
> > RTS threshold setting) for the fallback rates case.
> The idea behind the this part of minstrel_ht code is to avoid the
> overhead of RTS/CTS for transmissions using the primary rate and to
> increase the reliability of retransmissions by adding it for fallback
> rates. This is completely unrelated to the RTS threshold.
How does it avoid RTS/CTS (if it is set independent by RTS threshold
evaluation mac80211 and/or hardware driver)?
>
> If you don't want this behavior, I'm fine with adding a way to
> explicitly disable it. However, I do think leaving it on by default
> makes sense.
I expected this (as otherwise the flag setting would not be there) ;-)
Any hint how to implement an additional RTS/CTS on/off feature despite
the RTS threshold one for use explicit by minstrel_ht? Configure option,
module option, ...?
Regards,
Peter
>
> - Felix
next prev parent reply other threads:[~2021-11-26 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 21:28 [RFC v2] mac80211: minstrel_ht: do not set RTS/CTS flag for fallback rates Peter Seiderer
2021-11-26 12:47 ` Felix Fietkau
2021-11-26 14:25 ` Peter Seiderer [this message]
2021-11-29 8:34 ` 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=20211126152558.4d9fbce3@gmx.net \
--to=ps.report@gmx.net \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@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).