Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Received-SPF: pass (amphora.sui-inter.net: connection is authenticated)
Message-ID: <26f85a9f-552d-8420-0010-f5cda70d3a00@hqv.ch>
Date:   Fri, 6 Aug 2021 12:03:18 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.0
Subject: Re: [PATCH v2] rtl8xxxu: Fix the handling of TX A-MPDU aggregation
Content-Language: en-US
To:     chris.chiu@canonical.com
Cc:     code@reto-schneider.ch, linux-wireless@vger.kernel.org,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        jes.sorensen@gmail.com, kvalo@codeaurora.org, davem@davemloft.net,
        kuba@kernel.org
References: <20210804151325.86600-1-chris.chiu@canonical.com>
From:   Reto Schneider <rs@hqv.ch>
In-Reply-To: <20210804151325.86600-1-chris.chiu@canonical.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


Hi Chris,

On 8/4/21 17:13, chris.chiu@canonical.com wrote:
> The TX A-MPDU aggregation is not handled in the driver since the
> ieee80211_start_tx_ba_session has never been started properly.
> Start and stop the TX BA session by tracking the TX aggregation
> status of each TID. Fix the ampdu_action and the tx descriptor
> accordingly with the given TID.

I'd like to test this but I am not sure what to look for (before and 
after applying the patch).

What should I look for when looking at the (sniffed) Wireshark traces?

Kind regards,
Reto