DPDK usage discussions
 help / color / mirror / Atom feed
From: Carlos de Souza Moraes Neto <carlosmn@weg.net>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [E810 XXVDA4] timesync_read_tx_timestamp and timesync_read_rx_timestamp
Date: Fri, 11 Oct 2024 17:32:01 +0000	[thread overview]
Message-ID: <RO2P152MB6008A0B3F0F4325DD6335056DD792@RO2P152MB6008.LAMP152.PROD.OUTLOOK.COM> (raw)

Hi,
We have implemented a PTP peer-to-peer client running on the main core, with Lcores handling packet transmission and reception. However, we are encountering issues using the card's clock:
1. timesync_read_rx_timestamp: What should be the correct index value to use in this function?
2. timesync_read_tx_timestamp: This function consistently returns incorrect timestamps. Could it be registering the timestamp of a packet from another core if they are sending packets on a different port or queue of the same card?
3. rte_eth_timesync_read_time and rte_eth_timesync_adjust_time: Is there any inherent delay between calling read_time after adjust_time or write_time? Should we set a initial time when initializing dpdk?

Thank you for your help.

Best regards,
Carlos


                 reply	other threads:[~2024-10-11 17:51 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=RO2P152MB6008A0B3F0F4325DD6335056DD792@RO2P152MB6008.LAMP152.PROD.OUTLOOK.COM \
    --to=carlosmn@weg.net \
    --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).