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: Tue, 2 Jun 2020 15:18:11 -0400 [thread overview]
Message-ID: <CALEF-=DEorR3zUPukDgpq=of2q3uYtLzrK1XPDwqRi1YLWR50w@mail.gmail.com> (raw)
In-Reply-To: <AM4PR05MB3265F9A5814408F1E961ECDED2B00@AM4PR05MB3265.eurprd05.prod.outlook.com>
On Tue, May 26, 2020 at 12:00 PM Slava Ovsiienko
<viacheslavo@mellanox.com> wrote:
> ConnectX HW timestamp is the captured value of internal 64-bit counter running at the frequency,
> reported in the device_frequency_khz field of struct mlx5_ifc_cmd_hca_cap_bits{}.
> This structure is queried in mlx5_devx_cmd_query_hca_attr() routine.
I can't query this because "DevX is NOT supported".
As a matter of fact, mlx5dv_open_device() returns NULL.
Not sure if this limitation comes from HW/firmware config or capability.
* rdma-code, libibverbs-dev: 28.0
* NIC Part Number: MCX516A-CDA_Ax
* ConnectX-5 Ex EN
* FW: 16.25.1020
next prev parent reply other threads:[~2020-06-02 19:18 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 [this message]
2020-06-03 7:48 ` Slava Ovsiienko
2020-06-05 0:09 ` PATRICK KEROULAS
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:
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='CALEF-=DEorR3zUPukDgpq=of2q3uYtLzrK1XPDwqRi1YLWR50w@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 \
/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).