You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use hardware timestamping + libvma extended socket API (register_recv_callback).
When enabling SOL_SOCKET/SO_TIMESTAMPING/SOF_TIMESTAMPING_RAW_HARDWARE, the only way to get vma_info_t->hw_timestamp is to use it with conjunction with VMA_HW_TS_CONVERSION=1. Otherwise libvma returns ENODEV. I found this looking at the code.
My question now is how can I correlate the HW timestamp generated this way with system time? I could not find any documentation on that. And from my understanding SW timestamp is when the packet arrived to libvma/userland. My intention is to understand how long user land is "snoozing" while there is a packet on the wire.
The text was updated successfully, but these errors were encountered:
I'm trying to use hardware timestamping + libvma extended socket API (
register_recv_callback
).When enabling
SOL_SOCKET/SO_TIMESTAMPING/SOF_TIMESTAMPING_RAW_HARDWARE
, the only way to getvma_info_t->hw_timestamp
is to use it with conjunction withVMA_HW_TS_CONVERSION=1
. Otherwise libvma returnsENODEV
. I found this looking at the code.My question now is how can I correlate the HW timestamp generated this way with system time? I could not find any documentation on that. And from my understanding SW timestamp is when the packet arrived to libvma/userland. My intention is to understand how long user land is "snoozing" while there is a packet on the wire.
The text was updated successfully, but these errors were encountered: