From: "Brandes, Shai" <shaibran@amazon.com>
To: "dpdkuser77@gmail.com" <dpdkuser77@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Does DPDK provide RX timestamps?
Date: Mon, 9 Sep 2024 08:31:07 +0000 [thread overview]
Message-ID: <9ea0149e749043338d5a860c08c5106a@amazon.com> (raw)
In-Reply-To: <40e44bc0f788441ea70f48a33bef7f59@amazon.com>
> מאת: Dpdk Newbie <dpdkuser77@gmail.com
> <mailto:dpdkuser77@gmail.com> >
> תאריך: 9 בספט׳ 2024 01:32
> נושא: [EXTERNAL] Does DPDK provide RX timestamps?
> אל: dev@dpdk.org <mailto:dev@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.
>
[Brandes, Shai] Hi, currently AWS doesn’t 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 entire 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,
next prev parent reply other threads:[~2024-09-09 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 22:31 Dpdk Newbie
2024-09-09 0:13 ` Stephen Hemminger
2024-09-09 8:23 ` fengchengwen
[not found] ` <8a180c35-c4fd-4760-a4fa-f7d3ff360fab@email.android.com>
[not found] ` <40e44bc0f788441ea70f48a33bef7f59@amazon.com>
2024-09-09 8:31 ` Brandes, Shai [this message]
2024-09-09 17:54 ` Dpdk Newbie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ea0149e749043338d5a860c08c5106a@amazon.com \
--to=shaibran@amazon.com \
--cc=dev@dpdk.org \
--cc=dpdkuser77@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).