From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7664C45E48; Fri, 13 Dec 2024 02:53:18 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 60EBD402EE; Fri, 13 Dec 2024 02:53:18 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id C9C8E40263 for ; Fri, 13 Dec 2024 02:53:16 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id B7EA945E89; Fri, 13 Dec 2024 02:53:16 +0100 (CET) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 23.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rpf@mail.ustc.edu.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: multipart/alternative; boundary=17340547960.c11c6.3466820 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17340547960.c11c6.3466820 Date: Fri, 13 Dec 2024 02:53:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1602 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=3D298&action=3Dedit 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=20 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=3D/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= =20 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@alleg= ro-packets.com/#t Please kindly ask if more information is needed to debug it. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.= --17340547960.c11c6.3466820 Date: Fri, 13 Dec 2024 02:53:16 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1602
Summary igc: hardware timestamp is always zero with RTE_ETH_RX_OFFLOA= D_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 29=
8 [details]
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=20
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=3D/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_f=
lows.pcap=20

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.
=20=20=20=20=20=20=20=20=20=20
= --17340547960.c11c6.3466820--