[DPDK/other Bug 1838] latencystats won't work well with Rx timestamping

[DPDK/other Bug 1838] latencystats won't work well with Rx timestamping

[bugzilla]

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.