From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-3.sys.kth.se (smtp-3.sys.kth.se [130.237.48.192]) by dpdk.org (Postfix) with ESMTP id BE05131FC for ; Tue, 27 Nov 2018 08:57:52 +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 666CB30E1; Tue, 27 Nov 2018 08:57:52 +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 VQygAnueIwJ8; Tue, 27 Nov 2018 08:57:51 +0100 (CET) Received: from exdb01.ug.kth.se (unknown [192.168.32.111]) by smtp-3.sys.kth.se (Postfix) with ESMTPS id AEB973009; Tue, 27 Nov 2018 08:57:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default; t=1543305471; bh=QIgO0ezlI52tJI2lVK76WJxiipYyHtCsQL9PeSYFeYM=; h=From:To:Subject:Date:References:In-Reply-To; b=E+YR1oHDuxTjTQdz97KulRrkCpN7Yy2SYoIbkC9NdvMNEPlRMJIocH0CgrzYFRfY0 Hao8MK+dcU+Ym8SVXcaMZMC1Q7gwPeaSA2PGDATRQ6lJ3jnlaZ/X8OPIQeOEnGGnKG L7MxYDwyKc/78I7PRfzK+LMhBUvdBj1tM75ZCIwI= Received: from exdb04.ug.kth.se (192.168.32.114) by exdb01.ug.kth.se (192.168.32.111) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 27 Nov 2018 08:57:51 +0100 Received: from exdb05.ug.kth.se (192.168.32.115) by exdb04.ug.kth.se (192.168.32.114) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 27 Nov 2018 08:57:50 +0100 Received: from exdb05.ug.kth.se ([192.168.32.115]) by exdb05.ug.kth.se ([192.168.32.115]) with mapi id 15.00.1367.000; Tue, 27 Nov 2018 08:57:50 +0100 From: Tom Barbette To: Anshu Boonapalli , "users@dpdk.org" Thread-Topic: [dpdk-users] MLX5 Rx HW Timestamp units Thread-Index: AQHUhfJLwgPQHqWYhk6L0vN3VJuJ0aVjQXcG Date: Tue, 27 Nov 2018 07:57:49 +0000 Message-ID: <1543305470209.67587@kth.se> References: In-Reply-To: Accept-Language: fr-FR, sv-SE, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [77.218.240.10] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] MLX5 Rx HW Timestamp units X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 07:57:52 -0000 Hi Anshu,=0A= =0A= No it's the value of an internal Clock. The frequency and the base are both= unknown.=0A= =0A= We have a patch that works (but must be reworked before submission to dev) = that allows to query the current device clock value. Then from there you ca= n derive the base and the frequency. I can send it to you if you wish.=0A= =0A= Tom=0A= ________________________________________=0A= De : users de la part de Anshu Boonapalli =0A= Envoy=E9 : mardi 27 novembre 2018 02:41=0A= =C0 : users@dpdk.org=0A= Objet : [dpdk-users] MLX5 Rx HW Timestamp units=0A= =0A= Anyone know the units of Rx HW timestamps MLX5 provides?=0A= =0A= I assumed nanoseconds but tests i have run don't match the nanosecond units= .=0A= =0A= Thanks,=0A= -Anshu=0A=