From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yong Wang <yongwang@vmware.com>, Jon DeVree <nuxi@vault24.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vmxnet3: fill in imissed stat with pktsRxOutOfBuf
Date: Sat, 14 Apr 2018 00:19:39 +0100 [thread overview]
Message-ID: <e23c8e3b-55a1-0fb1-9c58-bfa45ee632c7@intel.com> (raw)
In-Reply-To: <44CC93ED-1286-4AC5-8C6D-8C6AFBD38A51@vmware.com>
On 4/11/2018 6:02 AM, Yong Wang wrote:
> 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>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-04-13 23:19 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
2018-04-13 23:19 ` Ferruh Yigit [this message]
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=e23c8e3b-55a1-0fb1-9c58-bfa45ee632c7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=nuxi@vault24.org \
--cc=yongwang@vmware.com \
/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).