From: Kalle Valo <kvalo@kernel.org>
To: Chris Chiu <chris.chiu@canonical.com>
Cc: Jes.Sorensen@gmail.com, davem@davemloft.net, kuba@kernel.org,
code@reto-schneider.ch, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtl8xxxu: Improve the A-MPDU retransmission rate with RTS/CTS protection
Date: Tue, 07 Dec 2021 09:10:32 +0200 [thread overview]
Message-ID: <87ee6oubyv.fsf@codeaurora.org> (raw)
In-Reply-To: <20211205095836.417258-1-chris.chiu@canonical.com> (Chris Chiu's message of "Sun, 5 Dec 2021 17:58:36 +0800")
Chris Chiu <chris.chiu@canonical.com> writes:
> The A-MPDU retransmission rate is always high (> 20%) even in a very
> clean environment. However, the vendor driver retransimission rate is
> < 10% in the same test bed. The different is the vendor driver starts
> the A-MPDU TXOP with initial RTS/CTS handshake which is observed in the
> air capture and the TX descriptor. Since there's no related field in
> TX descriptor to enable the L-SIG TXOP protection and the duration,
> applying the RTS/CTS protection instead helps to lower the retransmission
> rate from > 20% to ~12% in the same test setup.
>
> Signed-off-by: Chris Chiu <chris.chiu@canonical.com>
You should have marked this as v2 because you submitted already before:
https://patchwork.kernel.org/project/linux-wireless/patch/20211129143953.369557-1-chris.chiu@canonical.com/
And include a list of changes between versions, more info in the wiki
below.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-12-07 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 9:58 [PATCH] rtl8xxxu: Improve the A-MPDU retransmission rate with RTS/CTS protection Chris Chiu
2021-12-07 7:10 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-29 14:39 Chris Chiu
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=87ee6oubyv.fsf@codeaurora.org \
--to=kvalo@kernel.org \
--cc=Jes.Sorensen@gmail.com \
--cc=chris.chiu@canonical.com \
--cc=code@reto-schneider.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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).