Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp438052ybl; Fri, 23 Aug 2019 03:12:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqxGPJlYS9Rv2Cnf6KV+GUTRgq2/C9ACszYL5PIf8uEXG6ocxtsimjjV7sKrVRzkhe2lxIps X-Received: by 2002:a17:90a:d797:: with SMTP id z23mr4412751pju.43.1566555148798; Fri, 23 Aug 2019 03:12:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566555148; cv=none; d=google.com; s=arc-20160816; b=C+212thU8AxFAgE3UIUkHV3ACrsAzCyX1icVR/PEK812ktnzuaYZqxkkJwMPbMQuGN f0bKqmTufwX3YZv784uN6KSOGxCxwjeG03ArwBWJfplXyk4viE10UpwNEzgGDAxCA5Ts Kh77ovCDpBYLI7/tVXSmRwi03qlh9BaBvMJUFQZK1n1KgCJYvbmM24XWfutMIPCkSdeZ 5r1OuAznh9sNYkp1H2PvzIss1eiotZYPUPX5GDV4NtAvXND1Dywdq5lCLfM3m3WGP5ZX 2QmxvNlgtMqRGhDrbsP5kY/OUP+hOkrul5bxlnnrU/r5NLpzPKcMOrX5ylVL6Dq0cO7t Q1Kw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=/XSWpF+foN8Oyue2HrNOs5kfyL5oaANP7lQ97dmuIkI=; b=CYei6rbEk7z7uh5parRlxjMsID7lgMBPzEaQk1tBQvM33PSPSSWmPJmiAs71maPe1E YxSmFJSZEV1cEl9RFtt07mMiaiHKNGbam3Im6xzPa6pVX4KrLR6f1YU6FqbbBJx5HuFO HjbDVu3ncYnTr2So0O5QRriTKipD8P3fJQAH02PuGh3LtScFYPqcWAo3LGXbwOY62gsF rQ2NEWSAiucX4lKq93QM6HwHYe7JmKic0b4UmLoInTqx2Y3I/ZCGxQUR80u8Tlv5CaUs 2BNkAOuwWF69IGpueFKnf5QOWppA+ygy/F0JnZFhV5x1CwDQo5eWMeW1QyVXo3i9B2JP cc/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y190si2288198pfy.62.2019.08.23.03.12.13; Fri, 23 Aug 2019 03:12:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389565AbfHWHJ7 (ORCPT + 99 others); Fri, 23 Aug 2019 03:09:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44324 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388050AbfHWHJ7 (ORCPT ); Fri, 23 Aug 2019 03:09:59 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 117AA102700F; Fri, 23 Aug 2019 07:09:59 +0000 (UTC) Received: from localhost (unknown [10.43.2.236]) by smtp.corp.redhat.com (Postfix) with ESMTP id ADC2C5D6B2; Fri, 23 Aug 2019 07:09:58 +0000 (UTC) From: Stanislaw Gruszka To: linux-wireless@vger.kernel.org Cc: Felix Fietkau , Daniel Golle , =?UTF-8?q?Tomislav=20Po=C5=BEega?= , Mathias Kresin Subject: [PATCH] rt2x00: do not set IEEE80211_TX_STAT_AMPDU_NO_BACK on tx status Date: Fri, 23 Aug 2019 09:09:56 +0200 Message-Id: <1566544196-20371-1-git-send-email-sgruszka@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.redhat.com [10.5.110.66]); Fri, 23 Aug 2019 07:09:59 +0000 (UTC) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org According to documentation IEEE80211_TX_STAT_AMPDU_NO_BACK is suppose to be used when we do not recive BA (BlockAck). However on rt2x00 we use it when remote station fail to decode one or more subframes within AMPDU (some bits are not set in BlockAck bitmap). Setting the flag result in sent of BAR (BlockAck Request) frame and this might result of abuse of BA session, since remote station can sent BA with incorrect sequence numbers after receiving BAR. This problem is visible especially when connecting two rt2800 devices. Previously I observed some performance benefits when using the flag when connecting with iwlwifi devices. But currently possibly due to reacent changes in rt2x00 removing the flag has no effect on those test cases. So remove the IEEE80211_TX_STAT_AMPDU_NO_BACK. Signed-off-by: Stanislaw Gruszka --- drivers/net/wireless/ralink/rt2x00/rt2x00dev.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/net/wireless/ralink/rt2x00/rt2x00dev.c b/drivers/net/wireless/ralink/rt2x00/rt2x00dev.c index 9d158237ac67..c3eab767bc21 100644 --- a/drivers/net/wireless/ralink/rt2x00/rt2x00dev.c +++ b/drivers/net/wireless/ralink/rt2x00/rt2x00dev.c @@ -371,9 +371,6 @@ static void rt2x00lib_fill_tx_status(struct rt2x00_dev *rt2x00dev, IEEE80211_TX_CTL_AMPDU; tx_info->status.ampdu_len = 1; tx_info->status.ampdu_ack_len = success ? 1 : 0; - - if (!success) - tx_info->flags |= IEEE80211_TX_STAT_AMPDU_NO_BACK; } if (rate_flags & IEEE80211_TX_RC_USE_RTS_CTS) { -- 1.9.3