From: 최영민 <youngminchoi94@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Understanding of 'rx_errors" counter
Date: Thu, 1 Jul 2021 11:52:05 +0900 [thread overview]
Message-ID: <CAJzpdK5DUhbKJi0Q+8NZ461wq8rDNhF+KCMvAUv70gahir_5Ww@mail.gmail.com> (raw)
Hi, dpdk.
I'm trying to develop custom application using DPDK but I have a problem
now.
When I use multi-core for my application, 'rx_errors' counter increases. I
set one rx, tx queue per core and get counter information using
rte_eth_get_xstats(). I'm using DPDK version 20.05 and tried with 21.05 but
the same result happens. I'm using Mellanox BF-2 SmartNIC, and mlx5 NIC
driver. I ran my application both on host CPU and embedded ARM core of
SmartNIC. But, problem happens at host CPU(increasing 'rx_errors" counter).
Here is the full list of counter that I got using rte_eth_get_xstats().
Port 0: _______ rx_good_packets: 587188
Port 0: _______ tx_good_packets: 587696
Port 0: _______ rx_good_bytes: 45797374
Port 0: _______ tx_good_bytes: 38833365
Port 0: _______ rx_errors: 16
Port 0: _______ rx_q0packets: 1380
Port 0: _______ rx_q0bytes: 104803
Port 0: _______ rx_q1packets: 585808
Port 0: _______ rx_q1bytes: 45692571
Port 0: _______ rx_q1errors: 16
Port 0: _______ tx_q0packets: 1480
Port 0: _______ tx_q0bytes: 116271
Port 0: _______ tx_q1packets: 586216
Port 0: _______ tx_q1bytes: 38717094
Port 0: _______ rx_port_unicast_packets: 587346
Port 0: _______ rx_port_unicast_bytes: 48176028
Port 0: _______ tx_port_unicast_packets: 587696
Port 0: _______ tx_port_unicast_bytes: 38833301
Port 0: _______ rx_port_multicast_packets: 1
Port 0: _______ rx_port_multicast_bytes: 97
Port 0: _______ tx_packets_phy: 588288
Port 0: _______ rx_packets_phy: 588267
Port 0: _______ tx_bytes_phy: 42102136
Port 0: _______ rx_bytes_phy: 49473416
Port 0: _______ rx_64_bytes_phy: 672
Port 0: _______ rx_65_to_127_bytes_phy: 586398
Regards
Youngmin Choi
reply other threads:[~2021-07-01 2:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJzpdK5DUhbKJi0Q+8NZ461wq8rDNhF+KCMvAUv70gahir_5Ww@mail.gmail.com \
--to=youngminchoi94@gmail.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).