DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yong Wang <yongwang@vmware.com>
To: Jon DeVree <nuxi@vault24.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vmxnet3: fill in imissed stat with pktsRxOutOfBuf
Date: Wed, 11 Apr 2018 05:02:17 +0000	[thread overview]
Message-ID: <44CC93ED-1286-4AC5-8C6D-8C6AFBD38A51@vmware.com> (raw)
In-Reply-To: <20180407172952.6164-1-nuxi@vault24.org>

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


  reply	other threads:[~2018-04-11  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 17:29 Jon DeVree
2018-04-11  5:02 ` Yong Wang [this message]
2018-04-13 23:19   ` Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44CC93ED-1286-4AC5-8C6D-8C6AFBD38A51@vmware.com \
    --to=yongwang@vmware.com \
    --cc=dev@dpdk.org \
    --cc=nuxi@vault24.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).