From: Dpdk Newbie <dpdkuser77@gmail.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: users@dpdk.org
Subject: Re: Does DPDK provide RX timestamps?
Date: Mon, 9 Sep 2024 00:21:12 +0100 [thread overview]
Message-ID: <CAJgPhrr5jM03pcfni70hrwLrW8oMrxTBqkZhfq3oJrSBxtAuEw@mail.gmail.com> (raw)
In-Reply-To: <20240909020719.4d23c1dd@sovereign>
Thank you for the clarification regarding hardware/NIC timestamp on
i210 and ENA.
Does DPDK take a timestamp to facilitate my second measurement, from
the packet ring buffer to my application?
On Mon, 9 Sept 2024 at 00:07, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
>
> 2024-09-08 23:34 (UTC+0100), Dpdk Newbie:
> > 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,
>
> DPDK only provides API to access Rx timestamp if it's available.
> Example: https://elixir.bootlin.com/dpdk/v24.07/source/app/test-pmd/util.c#L37
>
> Rx timestamp availability depends on the PMD and HW.
> Support matrix: https://doc.dpdk.org/guides/nics/overview.html
> It seems to be no support for i210 (igb?) or AWS ENA (ena).
>
>
prev parent reply other threads:[~2024-09-08 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJgPhro2CF2gzouZmz0seKDzNej540GzuA_UyCGpG_zZT2gCwA@mail.gmail.com>
2024-09-08 22:34 ` Dpdk Newbie
2024-09-08 23:07 ` Dmitry Kozlyuk
2024-09-08 23:21 ` Dpdk Newbie [this message]
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=CAJgPhrr5jM03pcfni70hrwLrW8oMrxTBqkZhfq3oJrSBxtAuEw@mail.gmail.com \
--to=dpdkuser77@gmail.com \
--cc=dmitry.kozliuk@gmail.com \
--cc=users@dpdk.org \
/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).