From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1898] net/iavf: random packet reception delays with RTE_ETH_RX_OFFLOAD_TIMESTAMP
Date: Thu, 26 Feb 2026 09:09:31 +0000 [thread overview]
Message-ID: <bug-1898-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1898
Bug ID: 1898
Summary: net/iavf: random packet reception delays with
RTE_ETH_RX_OFFLOAD_TIMESTAMP
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: david.marchand@redhat.com
Target Milestone: ---
Random latency for some packets has been observed when polling from some IAVF
device.
The PF driver is a RHEL9.6 kernel ice driver.
This issue was observed after a kernel upgrade and bisecting points at kernel
commit "7c1178a9df58 ("ice: support Rx timestamp on flex descriptor")".
Our understanding is that following this change, the PF announces the
VIRTCHNL_VF_CAP_PTP capability, which then allows using
RTE_ETH_RX_OFFLOAD_TIMESTAMP on the DPDK driver side.
Disabling RTE_ETH_RX_OFFLOAD_TIMESTAMP on the application side made the random
latency issue disappear.
Looking at the Rx path for the iavf driver, a (frequent) call to
iavf_get_phc_time() can be noticed which is likely the cause of the random
slowdowns.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-02-26 9: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-1898-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.