From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1336] Statistic counter rx_missed_errors always shows zero no matter how large the traffic was generated on Mellanox NICs
Date: Tue, 19 Dec 2023 11:09:05 +0000 [thread overview]
Message-ID: <bug-1336-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1336
Bug ID: 1336
Summary: Statistic counter rx_missed_errors always shows zero
no matter how large the traffic was generated on
Mellanox NICs
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: pony.ma@ericsson.com
Target Milestone: ---
Created attachment 266
--> https://bugs.dpdk.org/attachment.cgi?id=266&action=edit
dpdk imitation log in data-plane pod
Our product used the DPDK as a lib for data-plane pod in the vcloud platform.
We observed that if data-plane pod doesn't mount the host path /sys/device to
the container, then "rx_missed_errors" counter always shows zero no matter how
large the traffic was generated on Mellanox NIC. But our customers don't like
application need to access any host paths, therefore we have to remove the
mount path /sys/device.
The outcome is data-plane pod would miss the "rx_missed_errors" metric, it
might have a degradation regarding the debuggability for packet loss.
I have got through the dpdk code about the function "mlx5_os_read_dev_stat",
and gdb the dpdk process. It shows that the point of "priv-gcounters" is NULL
and below two paths have no file of "out_of_buffer"
(gdb) p priv->q_counters
$4 = (struct mlx5_devx_obj *) 0x0
(gdb) info local
mkstr_size_path1 = 54
path1 = "/sys/class/infiniband/mlx5_2/hw_counters/out_of_buffer"
mkstr_size_path = 62
path = "/sys/class/infiniband/mlx5_2/ports/1/hw_counters/out_of_buffer"
Note: Our NIC is Mellanox and SRIOV VFs are used for POD.
We expect that Statistic counter "rx_missed_errors" can work well without
mounting host path /sys/device on Mellanox NICs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4169 bytes --]
reply other threads:[~2023-12-19 11:09 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=bug-1336-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).