From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: DPDK timestamping
Date: Wed, 24 Jan 2024 04:32:59 +0000 [thread overview]
Message-ID: <PH0PR01MB6730BD32685C19725813F1948F7B2@PH0PR01MB6730.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Hi,
I have Linux Oracle 91 with DPDK 22.11. The Intel i226 is my focus and getting hardware timestamping working, where I can retrieve the timestamp value for each packet and reorder packets from multiple i226 devices to single ring buffer. The Intel i226 datasheet says it supports hardware timestamping (per-packet timestamp). When I enable Rx offload timestamping (rxmode.offloads = RTE_ETH_RX_OFFLOAD_TIMESTAMP) I no longer see packets arrive when call rte_eth_rx_burst().
When I check the devinfo.rx_offload_capa value I see a value of 0xb260f, where bit-14 (RTE_ETH_RX_OFFLOAD_TIMESTAMP) is not set. Why doesn't DPDK 22.11 support RTE_ETH_RX_OFFLOAD_TIMESTAMP when the i226 datasheet has timestamp registers?
How in DPDK can I read the i226 registers?
Any guidance would be much appreciated.
Thanks,
Ed
[-- Attachment #2: Type: text/html, Size: 2719 bytes --]
reply other threads:[~2024-01-24 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=PH0PR01MB6730BD32685C19725813F1948F7B2@PH0PR01MB6730.prod.exchangelabs.com \
--to=ed.lombardo@netscout.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).