* rte_eth_timesync_read_tx_timestamp on Intel 82599ES NIC
@ 2022-12-07 3:50 Fengkai Sun
0 siblings, 0 replies; only message in thread
From: Fengkai Sun @ 2022-12-07 3:50 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
I read that 82599ES family does support hardware timestamping, but when I
tried to read from it, it returned -EINVAL. Below is my code:
// port initialization excised
struct timespec tmp;
ret = rte_eth_timesync_enable(0);
printf("Enable tx timestamp: status %d\n", ret);
ret = rte_eth_timesync_read_tx_timestamp(0, &tmp);
printf("Get tx timestamp: status %d\n", ret);
And the output is:
Enable tx timestamp: status 0
Get tx timestamp: status -22
Why does it happen? I looked into `examples/ptpclient/ptpclient.c` and
found that no other requirement is needed to read the hardware timestamp.
FYI, I'm using Ubuntu 20.04, DPDK 21.05, and below is what devbind returns:
Network devices using DPDK-compatible driver
0000:04:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb'
0000:04:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb'
Thank you in advance!
[-- Attachment #2: Type: text/html, Size: 1604 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-12-12 11:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-07 3:50 rte_eth_timesync_read_tx_timestamp on Intel 82599ES NIC Fengkai Sun
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).