From patchwork Wed Feb 1 04:20:13 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Kalesh A P X-Patchwork-Id: 122773 X-Patchwork-Delegate: ajit.khaparde@broadcom.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3ED4341B96; Wed, 1 Feb 2023 05:23:30 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7106542D0E; Wed, 1 Feb 2023 05:23:18 +0100 (CET) Received: from relay.smtp-ext.broadcom.com (saphodev.broadcom.com [192.19.144.205]) by mails.dpdk.org (Postfix) with ESMTP id F4214427EE for ; Wed, 1 Feb 2023 05:23:16 +0100 (CET) Received: from dhcp-10-123-153-22.dhcp.broadcom.net (bgccx-dev-host-lnx2.bec.broadcom.net [10.123.153.22]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id 8C67CC0000F1; Tue, 31 Jan 2023 20:23:15 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com 8C67CC0000F1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1675225396; bh=MsyCIxbedLmlvbJeedjVxeMJniqAGKlLPZOBbKFTVR4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=lzsjlyHs7zjT9KojbFu5bXfEyy+GNhFV8tz5vEdcUCUPk6sYAw898H5rphCXZ7mWK j30NdI1XRAoXH89TTQ6Sw5s1T66E+MAHt8+71LMbjemsKk5gyNqBOp2bhHQAdaVQTI hz33IhcWv3dGgh1ZsTkhN95raEWG3rD0EEUMla6U= From: Kalesh A P To: dev@dpdk.org Cc: ferruh.yigit@amd.com, ajit.khaparde@broadcom.com Subject: [dpdk-dev] [PATCH 2/3] net/bnxt: fix Rx queue stats after queue stop and start Date: Wed, 1 Feb 2023 09:50:13 +0530 Message-Id: <20230201042014.23526-3-kalesh-anakkur.purayil@broadcom.com> X-Mailer: git-send-email 2.10.1 In-Reply-To: <20230201042014.23526-1-kalesh-anakkur.purayil@broadcom.com> References: <20230201042014.23526-1-kalesh-anakkur.purayil@broadcom.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org From: Mike Baucom The Rx queue stats are being reported incorrectly due to a workaround for ring counters sometimes being reported as zero. When a queue is stopped and started, the ring counter is reset to zero. The workaround interprets the zero as incorrect, and sets the reported ring count as the previously read value (from before the queue being restared). This shows up as negative counters in testpmd's "show fwd stats" command. The fix clears the prev counter for the queue when the queue is started. Fixes: 219842b9990c ("net/bnxt: workaround spurious zero stats in Thor") Cc: stable@dpdk.org Signed-off-by: Mike Baucom Reviewed-by: Somnath Kotur Reviewed-by: Kishore Padmanabha Reviewed-by: Randy Schacher Reviewed-by: Ajit Khaparde --- drivers/net/bnxt/bnxt_rxq.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/net/bnxt/bnxt_rxq.c b/drivers/net/bnxt/bnxt_rxq.c index fabbbd4..99758dd 100644 --- a/drivers/net/bnxt/bnxt_rxq.c +++ b/drivers/net/bnxt/bnxt_rxq.c @@ -471,6 +471,12 @@ int bnxt_rx_queue_start(struct rte_eth_dev *dev, uint16_t rx_queue_id) return -EINVAL; } + /* reset the previous stats for the rx_queue since the counters + * will be cleared when the queue is started. + */ + memset(&bp->prev_rx_ring_stats[rx_queue_id], 0, + sizeof(struct bnxt_ring_stats)); + /* Set the queue state to started here. * We check the status of the queue while posting buffer. * If queue is it started, we do not post buffers for Rx.