From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1602] igc: hardware timestamp is always zero with RTE_ETH_RX_OFFLOAD_TIMESTAMP
Date: Fri, 13 Dec 2024 01:53:16 +0000 [thread overview]
Message-ID: <bug-1602-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1602
Bug ID: 1602
Summary: igc: hardware timestamp is always zero with
RTE_ETH_RX_OFFLOAD_TIMESTAMP
Product: DPDK
Version: 23.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: rpf@mail.ustc.edu.cn
Target Milestone: ---
Created attachment 298
--> https://bugs.dpdk.org/attachment.cgi?id=298&action=edit
Patch for rxtx_callbacks example to show hardware timestamp
I tried to use RTE_ETH_RX_OFFLOAD_TIMESTAMP with timestamp dynfield to get a
hardware timestamp on every packet. But it is always zero despite
RTE_ETH_RX_OFFLOAD_TIMESTAMP is supported for igc and enabled.
I encountered this problem in my own project. But this problem could be
reproduced with PktGen-DPDK and the rxtx_callbacks example.
My setup contains two ports (02:00.0 and 03:00.0) connected together on the
same machine:
I am generating traffic with pktgen-dpdk on port 02:00.0:
sudo env LD_LIBRARY_PATH=/opt/dpdk24/lib ./usr/local/bin/pktgen -l 0,1 -n 4 -b
03:00.0 --file-prefix pktgen -- -P -m "[1].0" -s 0:traces/small_flows.pcap
And receiving them on port 03:00.0:
sudo ./examples/dpdk-rxtx_callbacks -c 2 -n 3 -b 02:00.0 -- -t
The rxtx_callbacks examples is modified with the attached patch to show hw ts
in rx callbacks.
But for all the timestamps I get are zeros.
I am using uio_pci_generic with Intel Corporation Ethernet Controller I226-V
(rev 04).
I am aware that there's some problem with hardware timestamp for igc and has
applied this patch to my dpdk installation:
https://lore.kernel.org/dpdk-dev/00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com/#t
Please kindly ask if more information is needed to debug it. Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4266 bytes --]
reply other threads:[~2024-12-13 1:53 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=bug-1602-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.