Please see my comments inline.
I think it is a good solution: computationally inexpensive and accurate.I convinced myself that a viable way to measure timestamps between a request packet and its response packet can be the difference between two Intel rdtsc calls
The restrictions to valid use include:
- RTT (time difference) must be calculated on the same CORE
Yes, it is safe.
But I think it is also OK, if the two cores used for taking
sending TSC and receiving TSC belong to the same physical CPU. At
least it works me well in my measurement program called siitperf.
- fencing instructions (lfence) could be required
But it can also decrease the performance of your program.
I start the packet sender and receiver threads by the rte_eal_remote_launch() calls on the appropriate cores and it works fine for me.The time difference is OK provided,I think rdtsc does all this. But then I read [1]:
- it delivers at least microsecond resolution (rdtsc does)
- the difference is always positive (end-start) or zero
- the details of whether the clock runs or does not run at the processor speed is not material so long as there's sufficient resolution
- DPDK gives me the frequency rte_rdtsc_cycles(); this way I can convert from a rdtsc difference to elapsed time
- The OS doesn't reset the counter or pause it for interrupts or on halts
- The TSC is not always invariant
- And of course context switches (if a thread is not pinned to a core) will invalidate any time difference
I set the CPU clock frequency to a fixed value. (If I cannot do it from BIOS, I use the tlp Linux package.)So I am not so sure.
- The TSC is not incremented when the processor enters a deep sleep. I don't care about this because I'll turn off the power saving modes anyway
Now, of course, Mellanox can report time stamps. Is it actually possible to get HW NIC timestamps reported for every packet sent and received without overburdening the NIC? Based on what I can see for my case (Connect 4 LX) resolution is nanoseconds. So I am tempted to not fool around with rdtsc and just use NIC timestamps.
What is praxis in DPDK programming when one needs RTTs?
I have implemented both the Latency and PDV (Packet Delay Variation) measurements of RFC 8219 in siitperf using RDTSC. I am satisfied with the result.
If you are interested, you can find the source code here: https://github.com/lencsegabor/siitperf
And its latest version is documented in my paper: http://www.hit.bme.hu/~lencse/publications/ECC-2022-SFNATxy-Tester-published.pdf
Best regards,
Gábor