DPDK usage discussions
 help / color / mirror / Atom feed
From: Fengkai Sun <qcloud1014@gmail.com>
To: users@dpdk.org
Subject: rte_eth_timesync_read_tx_timestamp on Intel 82599ES NIC
Date: Wed, 7 Dec 2022 11:50:09 +0800	[thread overview]
Message-ID: <CAF6YOcPuxgap9Wk7WNYu368j3e2t_745Lk5-mY0z9yahqeiUSQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Hello list,

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'
drv=uio_pci_generic unused=ixgbe,vfio-pci
0000:04:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb'
drv=uio_pci_generic unused=ixgbe,vfio-pci
```

Thank you in advance!

--
Best Regards,
Fengkai

[-- Attachment #2: Type: text/html, Size: 1604 bytes --]

                 reply	other threads:[~2022-12-12 11:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF6YOcPuxgap9Wk7WNYu368j3e2t_745Lk5-mY0z9yahqeiUSQ@mail.gmail.com \
    --to=qcloud1014@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).