From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A309A45940
	for <public@inbox.dpdk.org>; Mon,  9 Sep 2024 00:35:10 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 7CACC402A8;
	Mon,  9 Sep 2024 00:35:10 +0200 (CEST)
Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com
 [209.85.210.182])
 by mails.dpdk.org (Postfix) with ESMTP id B7BE44026A
 for <users@dpdk.org>; Mon,  9 Sep 2024 00:35:08 +0200 (CEST)
Received: by mail-pf1-f182.google.com with SMTP id
 d2e1a72fcca58-717911ef035so2854153b3a.3
 for <users@dpdk.org>; Sun, 08 Sep 2024 15:35:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1725834908; x=1726439708; darn=dpdk.org;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=YrSCl84jMNsRx473XsKez2s6devJ7Ajtf8eLBhRj3/4=;
 b=DkW2awknrRxRUBg+Pgd5xzGh6S+IjWsK1cUdz6Pb68buckBgUapvcu8/h6dHFGZeO+
 Nc/k2EAD6U+MMf9WIvQjhaBQ+CSmBxlWpDiv2auChVGkmGGbEoLKq/sBL3gfVkV33N65
 4tG45tq17cpYeU1AammmmirNi5tWtnhkTGUhq/OUuup6TYd8oHTWTWHXI0gH7gLw9JSx
 QS16+hsprOEKPNE38WE4KSwuHN7S82S+TiYTM+c4Xqa03zZcGN+204Dkt7skNyO1uZWA
 qIG5xSRaQ1WMcrsdiEs6U1/S0GDrFDpGNxzhWTGjxhNjuJg3PTs3dZAg873gyVy7Kgak
 FnWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1725834908; x=1726439708;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=YrSCl84jMNsRx473XsKez2s6devJ7Ajtf8eLBhRj3/4=;
 b=fnszAabYT2oZhf+4lmGm7x5QfkBLXSsFnXIwketZ5/JLJDm/hO8Ckr3sBlWcW2EXhp
 4W4CuGCEQdExXGvn8PVGUH6x5K9PR9vQpVpIy1SG3fBG8I5bWBTqlA5LdE280hmMS1h8
 eWEq+tanIgsBqaAJw/6tk+njsWGTjwKjP8cydBXZDTDyk9MBkRTSgtdhDs3M9P9QQXOx
 p9nCYiULmXP3IHDQpohU4FVpUPvTOzudmpryJ860g4CefvodnxRLU6ZlnPLWBDqmQlXk
 ekpFZvSiRt30DQQx9O4Cbb6WHp0vbL81DQhWaAsO9Yfbg1ykg/4lpqINcT42nsmGLEN8
 hE0w==
X-Gm-Message-State: AOJu0YyVa2wLEpMviJ9NeJyqbph56DQTVL6hGU+TaBl3mRDIiRYOBmyP
 CSYM+ebhmqWwXe1YiQmBU8+Jb0vi/upDgAZt4H/SLtyzkTGH7maOVHRJj5YAmLb19XFeK1P2f1Q
 M12AdHTGKRGl+9DjZaiRlViN73vD5jA==
X-Google-Smtp-Source: AGHT+IG9klESZF4LVGyxvbsSFyoioU13bnDOPkSV0O2FlSTPInp1a+UpYVw8WZMvCGYvpwKahR8lKohZ4frUWAVbX4U=
X-Received: by 2002:a05:6a20:cfa4:b0:1ce:f0cc:e0dc with SMTP id
 adf61e73a8af0-1cf1d05a937mr9235723637.4.1725834907731; Sun, 08 Sep 2024
 15:35:07 -0700 (PDT)
MIME-Version: 1.0
References: <CAJgPhro2CF2gzouZmz0seKDzNej540GzuA_UyCGpG_zZT2gCwA@mail.gmail.com>
In-Reply-To: <CAJgPhro2CF2gzouZmz0seKDzNej540GzuA_UyCGpG_zZT2gCwA@mail.gmail.com>
From: Dpdk Newbie <dpdkuser77@gmail.com>
Date: Sun, 8 Sep 2024 23:34:56 +0100
Message-ID: <CAJgPhrpSBSrvV3C4YkD+AncAoHVBLwoWuDUrjkdE+xwKCXm6YQ@mail.gmail.com>
Subject: Does DPDK provide RX timestamps?
To: users@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

Hi. I am using Intel (i210) and AWS ENA network interface cards.

I would like to measure the following RX latencies:

1) NIC to DPDK packet ring buffer
2) DPDK packet ring buffer to application via rte_eth_rx_burst.

I don't mind measuring in nanoseconds or CPU cycles.

Unfortunately I cannot find any mention of hardware timestamps.

I found brief references to mbuf containing a timestamp in the dynamic
fields, but nothing definitive.

Could someone please clarify what the situation is?

Thanks,