From: Stephen Hemminger <stephen@networkplumber.org>
To: Mikael R Carlsson <Mikael.R.Carlsson@tietoevry.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Configure timestamp source for dpdk-pdump on E810 and DPDK 19.11
Date: Fri, 6 May 2022 07:55:27 -0700 [thread overview]
Message-ID: <20220506075527.2acefd5a@hermes.local> (raw)
In-Reply-To: <DU0PR04MB92261EA274F5EC329FE4E6CBA6C59@DU0PR04MB9226.eurprd04.prod.outlook.com>
On Fri, 6 May 2022 07:46:39 +0000
Mikael R Carlsson <Mikael.R.Carlsson@tietoevry.com> wrote:
> Hi!
>
> I am using a Intel E810-XXVDA4 and DPDK version 19.11. During troubleshooting we have captures outgoing traffic with dpdk-pdump:
>
> dpdk-pdump -- --pdump 'port=1,queue=*,tx-dev=/tmp/tx.pcap
>
> I have opened the pcap-file in wireshark and I can see that some packets are delayed. However, system behavior indicates that the delays I see in the pcap file are not correct, they are too big. My questions is, how is the timestamp on packets in the pcap from dpdk-pdump created, like NIC HW generated, CPU time at disk write etc. or something else? Are there any run-time or build-time options to change the source of the timestamps?
>
> / Mikael
>
>
>
The timestamp for packet capture in DPDK is done when packet is queued to
the device. It is not possible with current driver architecture to get
timestamp when/after the packet was transmitted.
next prev parent reply other threads:[~2022-05-06 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 7:46 Mikael R Carlsson
2022-05-06 14:55 ` Stephen Hemminger [this message]
2022-05-06 15:02 ` Stephen Hemminger
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=20220506075527.2acefd5a@hermes.local \
--to=stephen@networkplumber.org \
--cc=Mikael.R.Carlsson@tietoevry.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).