From: Thomas Monjalon <thomas@monjalon.net>
To: guyifan <guyifan@protonmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Kiran Vedere <kiranv@mellanox.com>,
erezf@mellanox.com, asafp@mellanox.com
Subject: Re: [dpdk-users] rte_eth_stats_get: imiss is not set when using mlx4/mlx5 driver
Date: Thu, 26 Mar 2020 22:02:09 +0100 [thread overview]
Message-ID: <10295895.BaYr0rKQ5T@xps> (raw)
In-Reply-To: <3y9Dhou4fuTvYRm4ap0SkN7XaRbAAJ18xOYRzOsNOV0XmCW-O95_pLcK4FfkkGslOxSSvF56vREIPgGXYFm7UDwZFGLRbAk8x4iLx6zwI2E=@protonmail.com>
Hi,
Sorry for the late answer.
22/10/2019 10:38, guyifan:
> DPDK version 18.11.2，imiss is always 0.
> And I could not find any code about 'imiss' in 'dpdk-stable-18.11.2/drivers/net/mlx5/' or 'dpdk-stable-18.11.2/drivers/net/mlx4/'.
> Is there any way to know how many packets have been dropped by a Mellanox NIC?
It is supported in DPDK 19.02:
http://git.dpdk.org/dpdk/commit/?id=ce9494d76c4783
and DPDK 18.11.3:
http://git.dpdk.org/dpdk-stable/commit/?h=81d0621264449ecc
prev parent reply other threads:[~2020-03-26 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 8:38 guyifan
2020-03-26 21:02 ` Thomas Monjalon [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=10295895.BaYr0rKQ5T@xps \
--to=thomas@monjalon.net \
--cc=asafp@mellanox.com \
--cc=erezf@mellanox.com \
--cc=guyifan@protonmail.com \
--cc=kiranv@mellanox.com \
--cc=users@dpdk.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).