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 A51DA42EB8; Wed, 19 Jul 2023 15:48:48 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6A7E640E25; Wed, 19 Jul 2023 15:48:48 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id BD9A640685 for ; Wed, 19 Jul 2023 15:48:46 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id ABEBA42EB9; Wed, 19 Jul 2023 15:48:46 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1266] net/mlx5: cannot create rte_flow rule matching ethernet multicast with jump action on bond mode 4 Date: Wed, 19 Jul 2023 13:48:46 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vojanec@cesnet.cz 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 Message-ID: Content-Type: multipart/alternative; boundary=16897745260.96A4cf.3747822 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 --16897745260.96A4cf.3747822 Date: Wed, 19 Jul 2023 15:48:46 +0200 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=3D1266 Bug ID: 1266 Summary: net/mlx5: cannot create rte_flow rule matching ethernet multicast with jump action on bond mode 4 Product: DPDK Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: vojanec@cesnet.cz Target Milestone: --- [DPDK Version] commit 238f67ca9cc00be4248b14d9ca4412edb7da62f6 (HEAD -> main, origin/main, origin/HEAD) Author: Ajit Khaparde Date: Wed Jul 12 11:05:30 2023 -0700 doc: update firmware version in bnxt guide Update earliest supported firmware version for 22.11 release. Signed-off-by: Ajit Khaparde [OS version] Operating System: Oracle Linux Server 8.7 Kernel: Linux 4.18.0-348.12.2.el8_5.x86_64 Architecture: x86-64 [DPDK build] meson build ninja -C build=20 [Network devices] 0000:3b:00.0 'MT2892 Family [ConnectX-6 Dx] 101d' if=3Dens1f0np0 drv=3Dmlx5= _core unused=3D=20 0000:3b:00.1 'MT2892 Family [ConnectX-6 Dx] 101d' if=3Dens1f1np1 drv=3Dmlx5= _core unused=3D=20 [OFED version] MLNX_OFED_LINUX-5.7-1.0.2.0 (OFED-5.7-1.0.2) [Reproduce in testpmd] ``` sudo ./dpdk-testpmd -a 0000:3b:00.0 -a 0000:3b:00.1 -c 0x0f -n 4 --vdev 'net_bonding0,slave=3D0000:3b:00.0,slave=3D0000:3b:00.1,mode=3D4,agg_mode= =3Dcount' -- -i --port-topology=3Dchained EAL: Detected CPU lcores: 40 EAL: Detected NUMA nodes: 2 EAL: Detected shared linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:3b:00.0 (socket 0) EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:3b:00.1 (socket 0) bond_ethdev_mode_set(1625) - Using mode 4, it is necessary to do TX burst a= nd RX burst at least every 100ms. TELEMETRY: No legacy callbacks, legacy socket not created Interactive-mode selected testpmd: create a new mbuf pool : n=3D171456, size=3D2176, socke= t=3D0 testpmd: preferred mempool ops selected: ring_mp_mc testpmd: create a new mbuf pool : n=3D171456, size=3D2176, socke= t=3D1 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) Port 0: 04:3F:72:C7:B8:84 Configuring Port 1 (socket 0) Port 1: 04:3F:72:C7:B8:85 Configuring Port 2 (socket 0) Device with port_id=3D0 already stopped Port 2: link state change event Device with port_id=3D1 already stopped Port 2: 04:3F:72:C7:B8:84 Checking link statuses... Done testpmd> flow create 2 group 0 priority 0 ingress pattern eth dst spec 01:00:00:00:00:00 dst mask 01:00:00:00:00:00 / end actions jump group 1 / e= nd bond_flow_create(104) - Failed to create flow on slave 0 port_flow_complain(): Caught PMD error type 1 (cause unspecified): hardware refuses to create flow: Invalid argument ``` [Notes] When using a different action, such as 'rss' or 'queue', the rule is created without any issues. When using a different ethernet mask, such as '0F:00:00:00:00:00', the rule= is also created. When using a different mode of the bonding PMD, the rules is created. --=20 You are receiving this mail because: You are the assignee for the bug.= --16897745260.96A4cf.3747822 Date: Wed, 19 Jul 2023 15:48:46 +0200 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 1266
Summary net/mlx5: cannot create rte_flow rule matching ethernet multi= cast with jump action on bond mode 4
Product DPDK
Version unspecified
Hardware x86
OS Linux
Status UNCONFIRMED
Severity normal
Priority Normal
Component ethdev
Assignee dev@dpdk.org
Reporter vojanec@cesnet.cz
Target Milestone --- 

[DPDK Version]
commit 238f67ca9cc00be4248b14d9ca4412edb7da62f6 (HEAD -> main, origin/ma=
in,
origin/HEAD)
Author: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date:   Wed Jul 12 11:05:30 2023 -0700

    doc: update firmware version in bnxt guide

    Update earliest supported firmware version for 22.11 release.

    Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

[OS version]
Operating System: Oracle Linux Server 8.7
Kernel: Linux 4.18.0-348.12.2.el8_5.x86_64
Architecture: x86-64

[DPDK build]
meson build
ninja -C build=20

[Network devices]
0000:3b:00.0 'MT2892 Family [ConnectX-6 Dx] 101d' if=3Dens1f0np0 drv=3Dmlx5=
_core
unused=3D=20
0000:3b:00.1 'MT2892 Family [ConnectX-6 Dx] 101d' if=3Dens1f1np1 drv=3Dmlx5=
_core
unused=3D=20

[OFED version]
MLNX_OFED_LINUX-5.7-1.0.2.0 (OFED-5.7-1.0.2)

[Reproduce in testpmd]
```
sudo ./dpdk-testpmd  -a 0000:3b:00.0 -a 0000:3b:00.1 -c 0x0f -n 4 --vdev
'net_bonding0,slave=3D0000:3b:00.0,slave=3D0000:3b:00.1,mode=3D4,agg_mode=
=3Dcount' --
-i --port-topology=3Dchained
EAL: Detected CPU lcores: 40
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:3b:00.0 (socket 0)
EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:3b:00.1 (socket 0)
bond_ethdev_mode_set(1625) - Using mode 4, it is necessary to do TX burst a=
nd
RX burst at least every 100ms.
TELEMETRY: No legacy callbacks, legacy socket not created
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=3D171456, size=3D2176,=
 socket=3D0
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mb_pool_1>: n=3D171456, size=3D2176,=
 socket=3D1
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
Port 0: 04:3F:72:C7:B8:84
Configuring Port 1 (socket 0)
Port 1: 04:3F:72:C7:B8:85
Configuring Port 2 (socket 0)
Device with port_id=3D0 already stopped

Port 2: link state change event
Device with port_id=3D1 already stopped
Port 2: 04:3F:72:C7:B8:84
Checking link statuses...
Done

testpmd> flow create 2 group 0 priority 0 ingress pattern eth dst spec
01:00:00:00:00:00 dst mask 01:00:00:00:00:00 / end actions jump group 1 / e=
nd
bond_flow_create(104) - Failed to create flow on slave 0
port_flow_complain(): Caught PMD error type 1 (cause unspecified): hardware
refuses to create flow: Invalid argument
```

[Notes]
When using a different action, such as 'rss' or 'queue', the rule is created
without any issues.
When using a different ethernet mask, such as '0F:00:00:00:00:00', the rule=
 is
also created.
When using a different mode of the bonding PMD, the rules is created.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16897745260.96A4cf.3747822--