Re: [dpdk-dev] [PATCH v4 3/3] rxtx_callbacks: Add support for HW timestamp

2019-06-12 Thread Thomas Monjalon
02/05/2019 21:11, Tom Barbette: > + if (hw_timestamping && ticks_per_cycle_mult == 0) { > + uint64_t cycles_base = rte_rdtsc(); > + uint64_t ticks_base; > + retval = rte_eth_read_clock(port, &ticks_base); > + if (retval != 0) > +

Re: [dpdk-dev] [PATCH v4 3/3] rxtx_callbacks: Add support for HW timestamp

2019-05-31 Thread Ferruh Yigit
On 5/2/2019 1:11 PM, Tom Barbette wrote: > Use rxtx callback to demonstrate a way to use rte_eth_read_clock to > convert the hardware timestamps to an amount of cycles. > > This allows to get the amount of time the packet spent since its entry > in the device. While the regular latency only shows

[dpdk-dev] [PATCH v4 3/3] rxtx_callbacks: Add support for HW timestamp

2019-05-02 Thread Tom Barbette
Use rxtx callback to demonstrate a way to use rte_eth_read_clock to convert the hardware timestamps to an amount of cycles. This allows to get the amount of time the packet spent since its entry in the device. While the regular latency only shows the latency from when it entered the software stack