From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 784] i40evf rx bytes statistics is losing 4 bytes per packet for vfs from same pf
Date: Mon, 09 Aug 2021 04:14:12 +0000 [thread overview]
Message-ID: <bug-784-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=784
Bug ID: 784
Summary: i40evf rx bytes statistics is losing 4 bytes per
packet for vfs from same pf
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: 839872562@qq.com
Target Milestone: ---
Recently, I found an interesting problem on i40evf(X710). It seems something is
wrong when using the interface i40evf_dev_stats_get to get bytes statistics.
1. When using vfs from two pfs for tx/rx, the bytes statistics is correct.
2. When using two vfs of the same pf for tx/rx, the rx bytes statistics is
losing 4 bytes per packet.
I have checked mbufs in the rx funcation, and the pkt_len is corrent in both
scenes. Seems it's related to CRC Strip, but needs further confirmation.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-08-09 4:14 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-784-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).