From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6606BA056A; Thu, 11 Mar 2021 11:05:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E2556406A2; Thu, 11 Mar 2021 11:05:21 +0100 (CET) Received: from smtp-3.sys.kth.se (smtp-3.sys.kth.se [130.237.48.192]) by mails.dpdk.org (Postfix) with ESMTP id 3ACAD40689 for ; Thu, 11 Mar 2021 11:05:21 +0100 (CET) Received: from smtp-3.sys.kth.se (localhost.localdomain [127.0.0.1]) by smtp-3.sys.kth.se (Postfix) with ESMTP id ED28F4FCB; Thu, 11 Mar 2021 11:05:20 +0100 (CET) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-3.sys.kth.se ([127.0.0.1]) by smtp-3.sys.kth.se (smtp-3.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8JQfccxbZvAu; Thu, 11 Mar 2021 11:05:20 +0100 (CET) X-KTH-Auth: barbette [78.129.119.184] DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default; t=1615457119; bh=QYpM41b8VguEHpryl/a8Kje0HX7rW6QClCuTIgVvS9c=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=aFV7Fi3kke5+VXIZ4klCrdWY0r3nutACWV30bpO/1RdmOggOTLe82Ax2EBoPoBLcW oqPzrxyHoKxT50w03Rtcb7z9O6eTbZZuPNQtKXkCF37rYClu/d6q/iLxifd8/nW6lg jmxWwBJwapxoH7YNIAoSZOAuRVf5aycAXZwE20No= X-KTH-mail-from: barbette@kth.se Received: from [192.168.1.90] (host-78-129-119-184.dynamic.voo.be [78.129.119.184]) by smtp-3.sys.kth.se (Postfix) with ESMTPSA id 051CE5C8B; Thu, 11 Mar 2021 11:05:18 +0100 (CET) To: Viacheslav Ovsiienko , dev@dpdk.org Cc: rasland@nvidia.com, matan@nvidia.com, orika@nvidia.com, thomas@monjalon.net References: <20210307100251.22538-1-viacheslavo@nvidia.com> From: Tom Barbette Message-ID: Date: Thu, 11 Mar 2021 11:05:19 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <20210307100251.22538-1-viacheslavo@nvidia.com> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040301000708010203070504" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-dev] [PATCH 0/5] mlx5: add timestamp format support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" This is a cryptographically signed message in MIME format. --------------ms040301000708010203070504 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 07-03-21 =C3=A0 11:02, Viacheslav Ovsiienko a =C3=A9crit=C2=A0: > There are two different timestamp formats can be provided potentially > by mlx5 supported hardware. > > The free-running format provides some opaque values captured from > internal clock counter clocked by some independent oscillator. > The free-running frequency is not pre-defined and should be queried > from the NIC. How is the UTC clock kept in sync with the host? It would be interesting = to mention a bit about that when you'll send the patch for the=20 "timestamp format context field", as it's important for precise=20 measurements. > > The real-time timestamps are presented in nanoseconds and captured from= > the dedicated UTC counter, that can be adjusted on the fly and might be= > synchronized with some external master clock. > > Depending on the version and configuration the hardware might support > either FR or RT timestamps, or both in the same time on per queue basis= =2E > Since firmware version xx.30.0256 the timestamp format can be configure= d > via fields in the queue context at the object creation time. For the > compatibility reasons the default zero value configures timestamps with= > free-running format. The NIC ConnectX-5 and earlier ones support the > free-running format only. Since ConnectX-6 both formats might be suppor= ted > and configured. The default zero value (specified in the non-defined > yet timestamp format context field) causes the queue creation > failure (rejected by firmware) if the NIC is configured to real-time ti= mestamp > format. Hence, it is crucial to check whether firmware/hardware support= s > timestamp formats and configure queues accordingly, and this patchset > also must be provided for stable DPDK releases. > > Compatibility affected (without this patchset) summary: > - ConnectX-6DX or BlueField 2 Your commit message mention CX6 but the compatibility summary CX6DX.=20 Which one started to get support? Thanks, Tom > - real-time format is configured in NV settings > - firmware is xx.30.0256 or higher > > Viacheslav Ovsiienko (5): > common/mlx5: add timestamp format support to DevX > net/mlx5: add timestamp format support > vdpa/mlx5: add timestamp format support > regex/mlx5: add timestamp format support > compress/mlx5: add timestamp format support > > drivers/common/mlx5/mlx5_devx_cmds.c | 35 +++++++++++++++++++-- > drivers/common/mlx5/mlx5_devx_cmds.h | 7 +++++ > drivers/common/mlx5/mlx5_prm.h | 41 ++++++++++++++++++++++--= - > drivers/compress/mlx5/mlx5_compress.c | 5 +++ > drivers/net/mlx5/linux/mlx5_os.c | 3 ++ > drivers/net/mlx5/mlx5.h | 3 ++ > drivers/net/mlx5/mlx5_devx.c | 12 +++++++- > drivers/net/mlx5/mlx5_flow_age.c | 10 ++++-- > drivers/net/mlx5/mlx5_txpp.c | 8 +++++ > drivers/net/mlx5/windows/mlx5_os.c | 3 ++ > drivers/regex/mlx5/mlx5_regex.c | 1 + > drivers/regex/mlx5/mlx5_regex.h | 1 + > drivers/regex/mlx5/mlx5_regex_control.c | 4 +++ > drivers/vdpa/mlx5/mlx5_vdpa.c | 1 + > drivers/vdpa/mlx5/mlx5_vdpa.h | 1 + > drivers/vdpa/mlx5/mlx5_vdpa_event.c | 8 +++++ > 16 files changed, 133 insertions(+), 10 deletions(-) > --------------ms040301000708010203070504--