From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1838] latencystats won't work well with Rx timestamping
Date: Fri, 28 Nov 2025 18:17:32 +0000 [thread overview]
Message-ID: <bug-1838-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1838
Bug ID: 1838
Summary: latencystats won't work well with Rx timestamping
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The DPDK API for receive timestamping is to have the device driver put the
timestamp in the dynamic field. This dynamic field is also used by the
latencystat library to measure the sojourn time through the application.
The conflict comes in because the device timestamp is in arbitrary device
clocks (see rte_eth_read_clock) and the latency stats library is assuming that
the timestamp in TSC (cpu clock).
One solution would be to use a different dynamic field for HW and TSC clock
values in the packet.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-11-28 18:17 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-1838-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).