DPDK usage discussions
 help / color / mirror / Atom feed
From: Pravein GK <praveingk@gmail.com>
To: Filip Janiszewski <contact@filipjaniszewski.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Intel XL710, timestamping
Date: Wed, 3 Mar 2021 16:53:33 +0530
Message-ID: <CAE4=sSeKYHRyhN0omebuX44WfFjgDk7ZTvO_8vNyL=KL4huhbA@mail.gmail.com> (raw)
In-Reply-To: <74675d87-d8c4-47ff-d80a-ff3c4cb0b5b3@filipjaniszewski.com>

Intel XL710 supports HW timestamping, however, it would work only on PTP
packets and not on normal packets.

Few things I would suggest :

1) Check if you enabled "CONFIG_RTE_LIBRTE_IEEE1588=y" in your
config/common_base when building dpdk.

2) Checkout
on how to enable the timesync.

3) Craft the packets using similar header as

I had used the same NIC, and it should work.


On Wed, Mar 3, 2021 at 4:07 PM Filip Janiszewski <
contact@filipjaniszewski.com> wrote:

> Hi,
> Is there a way to enable HW timestamps with this Intel card using DPDK
> by means of the IEEE1588 set of function API? (Dpdk 20.08).
> In my understanding the nic should support hardware time-stamping of RX
> packets if: "A separate PTP application would be required that
> communicates directly with the controller on the XL710" cit from
> https://community.intel.com/t5/Ethernet-Products/Does-intel-XL710-QDA2-support-HW-timestamping/m-p/563064
> Is there a way to make this work in DPDK? I'm honestly not sure what
> does it mean exactly "communicates directly with the controller", but I
> assume it has something to do with rte_eth_timesync_* ?
> I've actually tried already a test, I've executed
> rte_eth_timesync_enable/rte_eth_timesync_write_time and then verified
> with rte_eth_timesync_read_rx_timestamp if the timestamp is stored, and
> it seems it's there - but the packets are all coming with 0 in the
> timestamp field (mbuf)..
> Thanks
> --
> BR, Filip
> +48 666 369 823

      reply	other threads:[~2021-03-03 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 10:36 Filip Janiszewski
2021-03-03 11:23 ` Pravein GK [this message]

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:

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

  git send-email \
    --in-reply-to='CAE4=sSeKYHRyhN0omebuX44WfFjgDk7ZTvO_8vNyL=KL4huhbA@mail.gmail.com' \
    --to=praveingk@gmail.com \
    --cc=contact@filipjaniszewski.com \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git