DPDK patches and discussions
 help / color / mirror / Atom feed
From: PATRICK KEROULAS <patrick.keroulas@radio-canada.ca>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	 Shahaf Shuler <shahafs@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] mlx5 & pdump: convert HW timestamps to nanoseconds
Date: Thu, 4 Jun 2020 20:09:51 -0400	[thread overview]
Message-ID: <CALEF-=APTLw8y-2E8Tj=NRcXvgDEqUm8t-BYcGB8ZBc9Jtz53g@mail.gmail.com> (raw)
In-Reply-To: <VI1PR05MB3278C3AB381E70ACB5BC8F58D2880@VI1PR05MB3278.eurprd05.prod.outlook.com>

On Wed, Jun 3, 2020 at 3:48 AM Slava Ovsiienko <viacheslavo@mellanox.com> wrote:
> > From: PATRICK KEROULAS <patrick.keroulas@radio-canada.ca>
> > * rdma-code, libibverbs-dev: 28.0
> > * NIC Part Number:      MCX516A-CDA_Ax
> > * ConnectX-5 Ex EN
> > * FW: 16.25.1020
> It looks like outdated firmware, please:
> - update the firmware - at least 16.27.2008 is GA. I would recommend to install OFED - it updates the FW
> - make sure the UCTX_EN option in FW configuration is set to "true"

Hello Slava,

I managed to query device_frequency_khz by simply setting UCTX_EN=1,
convert the mbuf->timestamp to nsec and write a pcap. However, the
accuracy is quite disappointing, compared to libvma or even SW TS.

The freq value looks constant (=78125kHz). Correct me if I'm wrong, a
ptp client is supposed to continuously adjust some kind of VCO on the
NIC. And even setting a crazy value through /dev/ptp interface manually
doesn't affect device_frequency_khz. Please could you clarify?

This leads me back to mlx5dv_clock_info->nsec. If this is a valid method,
I think the only missing piece is to access it from the secondary process,
which implies to share ibv_context.

Best Regards,


  reply	other threads:[~2020-06-05  0:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:20 PATRICK KEROULAS
2020-05-21 15:33 ` Thomas Monjalon
2020-05-21 19:57   ` PATRICK KEROULAS
2020-05-21 20:09     ` Thomas Monjalon
2020-05-22 18:43       ` PATRICK KEROULAS
2020-05-26  7:44         ` Tom Barbette
2020-05-29 20:46           ` N. Benes
2020-05-26 16:00         ` Slava Ovsiienko
2020-05-29 20:56           ` PATRICK KEROULAS
2020-05-31 19:47             ` Slava Ovsiienko
2020-06-02 19:18           ` PATRICK KEROULAS
2020-06-03  7:48             ` Slava Ovsiienko
2020-06-05  0:09               ` PATRICK KEROULAS [this message]
2020-06-05 16:30                 ` Slava Ovsiienko

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='CALEF-=APTLw8y-2E8Tj=NRcXvgDEqUm8t-BYcGB8ZBc9Jtz53g@mail.gmail.com' \
    --to=patrick.keroulas@radio-canada.ca \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=viacheslavo@mellanox.com \
    --cc=vivien.didelot@gmail.com \


* 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).