* [DPDK/ethdev Bug 1840] net/pcap: missing read_clock operation
@ 2025-11-28 18:29 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2025-11-28 18:29 UTC (permalink / raw)
To: dev
http://bugs.dpdk.org/show_bug.cgi?id=1840
Bug ID: 1840
Summary: net/pcap: missing read_clock operation
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The pcap PMD provides receive timestamps from the pcap interface into the mbuf.
But there are a couple of issues with it.
The units of the timestamp are limited to microseconds now, but the pcap
library has a flag to provide nanosecond resolution. This should be used. One
caveat is that the API is misleading in reporting timestamp. The packet header
struct gives timestamp as a timeval (ie. usec) but if nanosecond mode flag is
used then the timestamp is really in timespec (ie nanoseconds).
The pcap PMD doesn't have a read_clock device operation so the application can
not determine the units of the receive timestamp. Pcap should behave like a
hardware PMD and return the underlying clock value.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-11-28 18:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-28 18:29 [DPDK/ethdev Bug 1840] net/pcap: missing read_clock operation bugzilla
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).