Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp118194pxb; Wed, 20 Apr 2022 17:39:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw9o+FZr7cYeKfT3BJtQAHBE2U/U1+8N2qTnrhMxZwBqg+ZUNqhEz/Mz3c7W0Z4yVDwyjXA X-Received: by 2002:a05:6402:274b:b0:423:fe73:95a0 with SMTP id z11-20020a056402274b00b00423fe7395a0mr12270077edd.224.1650501575684; Wed, 20 Apr 2022 17:39:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650501575; cv=none; d=google.com; s=arc-20160816; b=GqZ7+RJGCF2+4T2/JrGZKGQ0YXkNntPuTjhngc3qRiodFh4w2ak35N2y+0gHw6y9GP fAwgEmIJO4DJBDjTslOAMMQmNj3aLN2SWVt6M1jo80bjDtxePZBAb7J8mCgtMd0PXEj8 slO93Smok6FdyD5iqXsRHHtqPg+oc8iOO17ljnDhwG2MyyDjSJxX/pEJwqXM9LybQtxU dPzPdIka1kauRa7T3zC5waSKpV9Ht+i2oPLvHTFSyx/XCY415+TNOcJhGGaeRQp8q2Xn Ok49i0dorclFCE2gXgkC0bRIgA0NzHND7YcHzVJ7I87sFqOlBMK6c0Mdtemgt2mEnExv nwtA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:subject :from:references:cc:to:content-language:user-agent:mime-version:date :message-id:dkim-signature; bh=YAZC9y8BBhsm62CdLgduktz90VpmUPVlcKmGJkLc64w=; b=sJTqSGSTKpfdSZnMsRh11RGb+WUUclVYWTTNdVpiBl+mPI+MZ+lJecKBtxnJUqwm+q mAnZ0xVc14BisngSDP7Ncb9/04gl2Kmhhp98rRH0v3x9vy44Iqe7X3zn+C+B1cvZZDZq BRKYMOv5q3bHKsfqdpoEGYCBlOrLu6mfJwB8RGD2SknZExBEesfG1fzCYklQ1iG5xRMe +u6XjpGbFgsm6YYQbD7iUjBipCIOMU+ELL9W+mkCFYDld4q+bY1noY4g4TsuwqonAYva JcSk4h1cT+JtdQVz5BDrDPLFKiE30CtEtHsORVXXO5NLr+RVRGH7aYE/f+rM8ityNHju BFsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@nbd.name header.s=20160729 header.b="lA91Tk/4"; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id rp22-20020a170906d97600b006e89c09aeb7si2994854ejb.539.2022.04.20.17.39.12; Wed, 20 Apr 2022 17:39:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@nbd.name header.s=20160729 header.b="lA91Tk/4"; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346941AbiDTFXl (ORCPT + 66 others); Wed, 20 Apr 2022 01:23:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57386 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241585AbiDTFXk (ORCPT ); Wed, 20 Apr 2022 01:23:40 -0400 Received: from nbd.name (nbd.name [IPv6:2a01:4f8:221:3d45::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A3A8B3587B for ; Tue, 19 Apr 2022 22:20:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nbd.name; s=20160729; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:Subject: From:References:Cc:To:MIME-Version:Date:Message-ID:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=YAZC9y8BBhsm62CdLgduktz90VpmUPVlcKmGJkLc64w=; b=lA91Tk/4hnua5jf4aEIAWRR1sV WIKl9OGKQoW/fH/6ev9Qqb5GdhIJfDlbokw0y2slAZs+912GNSY4xQo5i0jMUZ6yriao4VVjeVRcU EDZoEJ5JRE2U/IIspZKQSzr68VZANu47JkOMKteLVHw3KomerHBP9OqnnpEQphZkz4xo=; Received: from p200300daa70ef200009e86881025829d.dip0.t-ipconnect.de ([2003:da:a70e:f200:9e:8688:1025:829d] helo=nf.local) by ds12 with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1nh2ll-00024n-85; Wed, 20 Apr 2022 07:20:49 +0200 Message-ID: Date: Wed, 20 Apr 2022 07:20:48 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Content-Language: en-US To: Bo Jiao Cc: linux-wireless , Ryder Lee , Sujuan Chen , Shayne Chen , Evelyn Tsai , linux-mediatek References: <20220420040346.8378-1-bo.jiao@mediatek.com> From: Felix Fietkau Subject: Re: [PATCH] mt76: mt7915: report qos_ctl without ACK policy In-Reply-To: <20220420040346.8378-1-bo.jiao@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 20.04.22 06:03, Bo Jiao wrote: > From: Bo Jiao > > there is no need to report to the mac80211 layer the ACK policy which may > cause rx out-of-order issue, because the hardware rmac module already handle it > > Signed-off-by: Bo Jiao > --- > drivers/net/wireless/mediatek/mt76/mt7915/mac.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/drivers/net/wireless/mediatek/mt76/mt7915/mac.c b/drivers/net/wireless/mediatek/mt76/mt7915/mac.c > index b47aea6..5080280 100644 > --- a/drivers/net/wireless/mediatek/mt76/mt7915/mac.c > +++ b/drivers/net/wireless/mediatek/mt76/mt7915/mac.c > @@ -675,6 +675,11 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb) > > fc = cpu_to_le16(FIELD_GET(MT_RXD6_FRAME_CONTROL, v0)); > qos_ctl = FIELD_GET(MT_RXD8_QOS_CTL, v2); > + /* > + * there is no need to report the ACK policy to the > + * mac80211 layer, because hw has already processed it. > + */ > + qos_ctl &= ~IEEE80211_QOS_CTL_ACK_POLICY_MASK; I don't understand this change at all. First of all, the qos_ctl field isn't really reported to the mac80211 layer, it's used in mt76 internally. The rx reorder code uses it to detect no-ack policy in order to avoid reordering for it. Since you're masking out the ack policy, the value will be IEEE80211_QOS_CTL_ACK_POLICY_NORMAL, which ends up forcibly enabling rx reordering, even when the policy indicates no-ack. How does this help, and what part does the rmac module already handle? - Felix