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 356054594A; Mon, 9 Sep 2024 19:54:26 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C8510410FD; Mon, 9 Sep 2024 19:54:25 +0200 (CEST) Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) by mails.dpdk.org (Postfix) with ESMTP id E2FB240ED0 for <dev@dpdk.org>; Mon, 9 Sep 2024 19:54:23 +0200 (CEST) Received: by mail-pg1-f176.google.com with SMTP id 41be03b00d2f7-7b8884631c4so2212161a12.2 for <dev@dpdk.org>; Mon, 09 Sep 2024 10:54:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725904463; x=1726509263; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=j5Io+RaAuygULl0o3ga7JMNd+H9gZ3SMan9Tu6ddf34=; b=eZVEu4lpFNrPMt0cuCCPn/8jUTP6RywI/vIgoIF9H3JCbOs7DwGi+WC+qPdt9j86Hk wsaoc0VnJ4lM5y8NBs2d1uVIHwoulMOA56QpoknpceY8KbQ4EbCFi08blYtZT6U77L4F 3nte6Q30tBLALdM48vG4aGQlqSVHyGqbq1v44fgldoj3PU9C5FyPcD7otrcwiPHabR7f VVURvN+dXBotEhJAOKpICdpXarDtDO9APpG/FhEuCUTX5Q2YdCoTluf4Zb1aN5drjTZc vpeeInbulPpdDyu+KXBMUHKURAqjnQy0FI3RdO4NxSf3YMdyoC0y0sTVwFTSUsijF9rD g4+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725904463; x=1726509263; h=content-transfer-encoding:cc: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=j5Io+RaAuygULl0o3ga7JMNd+H9gZ3SMan9Tu6ddf34=; b=O2BqaB4nC6gVYzo7L4stca+gGikmjd+RFiZhIS8W4lv0jxLZ0CLEKtGL1MUU7rhQn0 6yKAD1oOQhyIeZrGJ7B1Z71ra96L8jNXJrVo45BQfEQRnPadnISMm2Di0yrslabCkd8b dEy9V+mCNOZ7RR9oOIW2GGLAwhJ4GZyJ2z87dUWeQuE62iE5mhlezYRZfBrZAJQYZZ0G 8AhH/GZ5Zgc8hGsLVZ+Fq34tPPkE7JlzYEn8F+mBLvnro39/8UqlqPgCzoTzoi8Tv6WU Je4VfrvCm4r0z38UBwssE/fS/5FbkNIvbA1WkwFZkKZ+7lDpYgmY2HyK/5HBPStNls7t C74A== X-Gm-Message-State: AOJu0YwjTSWXw0Mmazjd7xWEbI3hrVWuMlgDborFDd791OikwrHlGs3B q1w/SVARbUNKTz5VxkhMeWmGSvz8QjvCgjmeuMjhXQbT9KRzwtCu8pJH5haN8mp7KLwpKz9rp84 DnLKM2UYKfjq0ZAAWnq6zR484bw8= X-Google-Smtp-Source: AGHT+IEFI8gmveBGGbIxDBFYo3SiGFJMUYXr5+r96G9Ej087vZ8EHT4wcoWyFzbKrLlFGuFWswu0LVmW0xysG6Jta/8= X-Received: by 2002:a17:90a:fe06:b0:2d8:859b:931c with SMTP id 98e67ed59e1d1-2dad50f3eddmr16697002a91.33.1725904462799; Mon, 09 Sep 2024 10:54:22 -0700 (PDT) MIME-Version: 1.0 References: <CAJgPhro2CF2gzouZmz0seKDzNej540GzuA_UyCGpG_zZT2gCwA@mail.gmail.com> <8a180c35-c4fd-4760-a4fa-f7d3ff360fab@email.android.com> <40e44bc0f788441ea70f48a33bef7f59@amazon.com> <9ea0149e749043338d5a860c08c5106a@amazon.com> In-Reply-To: <9ea0149e749043338d5a860c08c5106a@amazon.com> From: Dpdk Newbie <dpdkuser77@gmail.com> Date: Mon, 9 Sep 2024 18:54:10 +0100 Message-ID: <CAJgPhrotN5bvr=y8LWJO2KUVSY5AJCn0W1nvnJi+LUjBnfvK0A@mail.gmail.com> Subject: Re: Does DPDK provide RX timestamps? To: "Brandes, Shai" <shaibran@amazon.com> Cc: "dev@dpdk.org" <dev@dpdk.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 I was looking at the source code but I'm more OOP C++ than C. I found eth_ena_recv_pkts but is it possible for me to add a software timestamp before the mbuf is added to the ring buffer? This would be incredibly useful. On Mon, 9 Sept 2024 at 09:31, Brandes, Shai <shaibran@amazon.com> wrote: > > > > =D7=9E=D7=90=D7=AA: Dpdk Newbie <dpdkuser77@gmail.com > > <mailto:dpdkuser77@gmail.com> > > > =D7=AA=D7=90=D7=A8=D7=99=D7=9A: 9 =D7=91=D7=A1=D7=A4=D7=98=D7=B3 2024 0= 1:32 > > =D7=A0=D7=95=D7=A9=D7=90: [EXTERNAL] Does DPDK provide RX timestamps? > > =D7=90=D7=9C: dev@dpdk.org <mailto:dev@dpdk.org> > > =E2=80=8F=D7=A2=D7=95=D7=AA=D7=A7: > > > > > > > > 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. > > > [Brandes, Shai] Hi, currently AWS doesn=E2=80=99t 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 en= tire 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. > > > > > > 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, >