From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id E58F245948;
	Mon,  9 Sep 2024 10:31:16 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id D59C140691;
	Mon,  9 Sep 2024 10:31:16 +0200 (CEST)
Received: from smtp-fw-9106.amazon.com (smtp-fw-9106.amazon.com
 [207.171.188.206])
 by mails.dpdk.org (Postfix) with ESMTP id AE1CD402BB
 for <dev@dpdk.org>; Mon,  9 Sep 2024 10:31:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209;
 t=1725870676; x=1757406676;
 h=from:to:cc:date:message-id:references:in-reply-to:
 content-transfer-encoding:mime-version:subject;
 bh=DbjTiEKM59nZm0Y27eiw7PNKDZhZ5HMEwV/OOo4VcFo=;
 b=L26s7GSwRnbFleceCthGPNKKNo97rQcGyEAbJd3ILzIwx/PAG0wyAVAP
 Z6VeX9lE4rJgyFxPyK2tdFpV+neeDgF5quEpljvy4jjE1i9cT9JzxyIH1
 zZ9C/XarPQm338zI2w2zA3zQCzbnQNICFPAs/2O4AZFRghJxVg1c2Fcrs 4=;
X-IronPort-AV: E=Sophos;i="6.10,213,1719878400"; d="scan'208";a="757926743"
Subject: RE: Does DPDK provide RX timestamps?
Thread-Topic: Does DPDK provide RX timestamps?
Received: from pdx4-co-svc-p1-lb2-vlan2.amazon.com (HELO
 smtpout.prod.us-east-1.prod.farcaster.email.amazon.dev) ([10.25.36.210])
 by smtp-border-fw-9106.sea19.amazon.com with
 ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2024 08:31:09 +0000
Received: from EX19MTAEUA001.ant.amazon.com [10.0.17.79:40053]
 by smtpin.naws.eu-west-1.prod.farcaster.email.amazon.dev [10.0.13.102:2525]
 with esmtp (Farcaster)
 id 3e9c8ccb-fd3a-43c2-94b8-629d25056573; Mon, 9 Sep 2024 08:31:07 +0000 (UTC)
X-Farcaster-Flow-ID: 3e9c8ccb-fd3a-43c2-94b8-629d25056573
Received: from EX19D007EUA004.ant.amazon.com (10.252.50.76) by
 EX19MTAEUA001.ant.amazon.com (10.252.50.192) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.34;
 Mon, 9 Sep 2024 08:31:07 +0000
Received: from EX19D007EUA002.ant.amazon.com (10.252.50.68) by
 EX19D007EUA004.ant.amazon.com (10.252.50.76) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.35;
 Mon, 9 Sep 2024 08:31:07 +0000
Received: from EX19D007EUA002.ant.amazon.com ([fe80::1295:20d9:141e:47cc]) by
 EX19D007EUA002.ant.amazon.com ([fe80::1295:20d9:141e:47cc%3]) with
 mapi id 15.02.1258.035; Mon, 9 Sep 2024 08:31:07 +0000
From: "Brandes, Shai" <shaibran@amazon.com>
To: "dpdkuser77@gmail.com" <dpdkuser77@gmail.com>
CC: "dev@dpdk.org" <dev@dpdk.org>
Thread-Index: AQHbAj7++YnDNd0KKUiMznZ+b2aZOrJOz2B7gAAaf4CAADEjoA==
Date: Mon, 9 Sep 2024 08:31:07 +0000
Message-ID: <9ea0149e749043338d5a860c08c5106a@amazon.com>
References: <CAJgPhro2CF2gzouZmz0seKDzNej540GzuA_UyCGpG_zZT2gCwA@mail.gmail.com>
 <8a180c35-c4fd-4760-a4fa-f7d3ff360fab@email.android.com>
 <40e44bc0f788441ea70f48a33bef7f59@amazon.com>
In-Reply-To: <40e44bc0f788441ea70f48a33bef7f59@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.213.12]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org


> =EE=E0=FA: Dpdk Newbie <dpdkuser77@gmail.com
> <mailto:dpdkuser77@gmail.com> >
> =FA=E0=F8=E9=EA: 9 =E1=F1=F4=E8=D7 2024 01:32
> =F0=E5=F9=E0: [EXTERNAL] Does DPDK provide RX timestamps?
> =E0=EC: dev@dpdk.org <mailto:dev@dpdk.org>
> =FE=F2=E5=FA=F7:
>=20
>=20
>=20
> Hi. I am using Intel (i210) and AWS ENA network interface cards.
>=20
>=20
>=20
> I would like to measure the following RX latencies:
>=20
> 1) NIC to DPDK packet ring buffer
>=20
> 2) DPDK packet ring buffer to application via rte_eth_rx_burst.
>=20
[Brandes, Shai] Hi, currently AWS doesn=92t support HW timestamping.
In order to get the full Rx latency you need to measure rte_eth_rx_burst as=
 it is mapped to ENA driver routine eth_ena_recv_pkts which covers the enti=
re flow including NIC to DPDK packet ring buffer flow (ena_com_rx_pkt)

All the best
Shai

> I don't mind measuring in nanoseconds or CPU cycles.
>=20
>=20
> Unfortunately I cannot find any mention of hardware timestamps.
>=20
>=20
> I found brief references to mbuf containing a timestamp in the dynamic
> fields, but nothing definitive.
>=20
> Could someone please clarify what the situation is?
>=20
> Thanks,