DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Patrick Keroulas <patrick.keroulas@radio-canada.ca>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] [PATCH v1 0/3] pdump HW timestamps for mlx5
Date: Tue, 23 Jun 2020 15:07:15 +0000	[thread overview]
Message-ID: <AM4PR05MB3265D35802F8718C8E8E1E43D2940@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200609141713.11614-1-patrick.keroulas@radio-canada.ca>

Hi, Patrick.

Not all rdma-core versions provide the 
- mlx5dv_get_clock_info(context, clock_info);
- mlx5dv_ts_to_ns(clock_info, device_timestamp);

With these versions we would get compilation/linkage error.
There should be conditional compilation like it is done with other mlx5dv routines.

With best regards, Slava

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Patrick Keroulas
> Sent: Tuesday, June 9, 2020 17:17
> To: dev@dpdk.org
> Cc: Patrick Keroulas <patrick.keroulas@radio-canada.ca>
> Subject: [dpdk-dev] [RFC] [PATCH v1 0/3] pdump HW timestamps for mlx5
> 
> The intention is to produce a pcap with nanosecond precision when
> timestamp offloading is activated on mlx5 NIC.
> 
> The packets forwarded by testpmd hold the raw counter but a pcap requires
> a time unit. Assuming that the NIC clock is already synced with external
> master clock, this patchset simply integrates the nanosecond converter that
> is already implemented by ibverbs. The conversion is performed is pdump rx
> callback.
> 
> Patrick Keroulas (3):
>   net/mlx5: add timestamp-to-ns converter from libibverbs
>   ethdev: add API to convert raw timestamps to nsec
>   net/pcap: dump hardware timestamps
> 
>  drivers/common/mlx5/mlx5_glue.c          | 16 ++++++++++++
>  drivers/common/mlx5/mlx5_glue.h          |  4 +++
>  drivers/net/mlx5/mlx5.c                  |  1 +
>  drivers/net/mlx5/mlx5.h                  |  1 +
>  drivers/net/mlx5/mlx5_ethdev.c           | 30 ++++++++++++++++++++++
>  drivers/net/pcap/rte_eth_pcap.c          | 32 ++++++++++++++++--------
>  lib/librte_ethdev/rte_ethdev.c           | 12 +++++++++
>  lib/librte_ethdev/rte_ethdev.h           | 17 +++++++++++++
>  lib/librte_ethdev/rte_ethdev_core.h      |  5 ++++
>  lib/librte_ethdev/rte_ethdev_version.map |  2 ++
>  lib/librte_mbuf/rte_mbuf_core.h          |  3 ++-
>  lib/librte_pdump/rte_pdump.c             | 15 ++++++++++-
>  12 files changed, 126 insertions(+), 12 deletions(-)
> 
> --
> 2.17.1


      parent reply	other threads:[~2020-06-23 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 14:17 Patrick Keroulas
2020-06-09 14:17 ` [dpdk-dev] [RFC] [PATCH v1 1/3] net/mlx5: add timestamp-to-ns converter from libibverbs Patrick Keroulas
2020-06-09 14:17 ` [dpdk-dev] [RFC] [PATCH v1 2/3] ethdev: add API to convert raw timestamps to nsec Patrick Keroulas
2020-06-09 14:17 ` [dpdk-dev] [RFC] [PATCH v1 3/3] net/pcap: dump hardware timestamps Patrick Keroulas
2020-06-09 14:41   ` Ferruh Yigit
2020-06-10 13:51     ` Ferruh Yigit
2020-06-23 15:07 ` Slava Ovsiienko [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:
  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=AM4PR05MB3265D35802F8718C8E8E1E43D2940@AM4PR05MB3265.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=patrick.keroulas@radio-canada.ca \
    /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).