From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pinero.vault24.org (pinero.vault24.org [69.164.212.126]) by dpdk.org (Postfix) with ESMTP id 699A71C942 for ; Sat, 7 Apr 2018 19:29:57 +0200 (CEST) Received: from feynman.vault24.org (feynman.vault24.org [IPv6:2001:470:1f11:7b5::14]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by pinero.vault24.org (Postfix) with ESMTPS id B6B2860FB; Sat, 7 Apr 2018 13:29:56 -0400 (EDT) Received: by feynman.vault24.org (Postfix, from userid 1000) id 3BFE8402392A; Sat, 7 Apr 2018 13:29:56 -0400 (EDT) From: Jon DeVree To: dev@dpdk.org Cc: skhare@vmware.com, yongwang@vmware.com, Jon DeVree Date: Sat, 7 Apr 2018 13:29:52 -0400 Message-Id: <20180407172952.6164-1-nuxi@vault24.org> X-Mailer: git-send-email 2.17.0 Subject: [dpdk-dev] [PATCH] vmxnet3: fill in imissed stat with pktsRxOutOfBuf X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2018 17:29:57 -0000 This counter comes from a "hardware" register of the vmxnet3 device and seems to behave like the MPC (Missed Packet Count) register of the Intel NICs. So I think this data belongs in the imissed field rather than the rx_nombuf field. Signed-off-by: Jon DeVree --- drivers/net/vmxnet3/vmxnet3_ethdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c index 426008722..4ef2d7d3b 100644 --- a/drivers/net/vmxnet3/vmxnet3_ethdev.c +++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c @@ -1015,7 +1015,7 @@ vmxnet3_dev_stats_get(struct rte_eth_dev *dev, struct rte_eth_stats *stats) stats->q_errors[i] = rxStats.pktsRxError; stats->ierrors += rxStats.pktsRxError; - stats->rx_nombuf += rxStats.pktsRxOutOfBuf; + stats->imissed += rxStats.pktsRxOutOfBuf; } return 0; -- 2.17.0