From: Yoon Junghan <cerotyki@gmail.com>
To: users@dpdk.org
Subject: HW RX timestamp with LRO enabled on ConnectX-7 (DPDK 20.11)
Date: Tue, 22 Jul 2025 16:21:44 +0900 [thread overview]
Message-ID: <b05b756f-d8ea-4b2b-a8bf-ea309efeff21@Spark> (raw)
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Hello,
I'm currently using DPDK 20.11 with a ConnectX-7 NIC, and I'm trying to retrieve RX hardware timestamps using `rte_mbuf_dyn_rx_timestamp_register()`.
When LRO is enabled, I notice that LROed mbufs seem to share identical timestamp values, and the timestamps are unexpectedly large or inconsistent. This raises the question of whether LRO is interfering with the correctness of the RX HW timestamps.
I’d appreciate any clarification on whether HW RX timestamping is reliable when LRO is enabled on this platform, or if LRO should be just disabled for accurate per-packet timestamping.
Sincerely,
Junghan Yoon
[-- Attachment #2: Type: text/html, Size: 958 bytes --]
next reply other threads:[~2025-07-22 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 7:21 Yoon Junghan [this message]
2025-07-22 8:30 ` Ivan Malov
2025-07-22 8:46 ` Yoon Junghan
2025-07-23 12:43 ` Yoon Junghan
2025-07-23 13:09 ` Ivan Malov
2025-07-23 13:20 ` Yoon Junghan
2025-07-23 13:28 ` Ivan Malov
2025-07-23 13:50 ` Yoon Junghan
2025-07-23 14:19 ` Ivan Malov
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=b05b756f-d8ea-4b2b-a8bf-ea309efeff21@Spark \
--to=cerotyki@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).