On 4/7/18, 10:30 AM, "Jon DeVree" <n...@vault24.org> wrote:
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 <n...@vault24.org> --- Acked-by: Yong Wang <yongw...@vmware.com> 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