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 3896542861; Thu, 30 Mar 2023 12:46:02 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0CAF0410DC; Thu, 30 Mar 2023 12:46:02 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 070C240E25 for ; Thu, 30 Mar 2023 12:46:00 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id EC45F42870; Thu, 30 Mar 2023 12:45:59 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1205] iavf: cannot create 2 rte_flows with E810 VF, but can with E810 PF Date: Thu, 30 Mar 2023 10:46:00 +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.03 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maxime.leroy@6wind.com 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=16801731590.Fa0aafe.3218854 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 --16801731590.Fa0aafe.3218854 Date: Thu, 30 Mar 2023 12:45:59 +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=3D1205 Bug ID: 1205 Summary: iavf: cannot create 2 rte_flows with E810 VF, but can with E810 PF Product: DPDK Version: 23.03 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: maxime.leroy@6wind.com Target Milestone: --- Environnement ------------- distribution for host/vm: Ubuntu 22.04.2 LTS, kernel 5.15.0-67-generic kernel driver: 1.10.1.2.2 firmware-version: 4.10 0x80015191 1.3310.0 COMMS DDP: 1.3.37 ICE OS Default Package version 1.3.30.0 testpmd cmdline: ./build/app/dpdk-testpmd --log-level=3D.*ice.*,debug --legacy-mem -c 7 -a 17:00.0 -a 0000:17:00.1 -- -i --nb-cores=3D2 --nb-po= rts=3D2 --total-num-mbufs=3D2048 dpdk version: 23.03.0-rc4 NIC: Intel Corporation Ethernet Controller E810-C for QSFP=20 With PF (ice pmd) ----------------- Working case, no sriov, no VM.=20 ICE PMD is able to create the following flows: ./build/app/dpdk-testpmd --log-level=3D.*ice.*,debug --legacy-mem -c 7 -a 1= 7:00.0 -a 0000:17:00.1 -- -i --nb-cores=3D2 --nb-ports=3D2 --total-num-mbufs=3D2= 048 testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions queue index 0 / end ice_flow_create(): Succeeded to create (2) flow Flow rule #0 created testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end=20 actions queue index 0 / end ice_flow_create(): Succeeded to create (2) flow Flow rule #1 created With VF (iavf pmd) ------------------ No working case sriov with a VM on the same device/hardware. sriov devices: On PF : echo 1 > "/sys/bus/pci/devices/0000:17:00.0/sriov_numvfs" -> for VF 17.01.0 On PF : echo 1 > "/sys/bus/pci/devices/0000:17:00.1/sriov_numvfs" -> for VF 17.11.0 QEMU ARGS: -device vfio-pci,host=3D0000:17:01.0,addr=3D04 -device vfio-pci,host=3D0000:17:11.0,addr=3D05=20 ./build/app/dpdk-testpmd --log-level=3D.*iavf.*,debug -c 0x6 -a 0000:00:0= 4.0 -a 0000:00:05.0 -- -i --total-num-mbufs=3D2048 testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions queue index 0 / end iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 47 iavf_fdir_add(): Succeed in adding rule request by PF iavf_flow_create(): Succeeded to create (2) flow Flow rule #0 created testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end=20 actions queue index 0 / end iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 47 iavf_fdir_add(): Failed to add rule request due to the rule is conflict with existing rule iavf_flow_create(): Failed to create flow port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Failed = to create parser engine.: Invalid argument Conclusion ---------- IAVF is not able to create the second flow. Because the kernel driver 1.10.1.2.2 rejects the creation of second flow. There are no such issue with ICE pmd of dpdk 23.03.0-rc4. --=20 You are receiving this mail because: You are the assignee for the bug.= --16801731590.Fa0aafe.3218854 Date: Thu, 30 Mar 2023 12:45:59 +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 1205
Summary iavf: cannot create 2 rte_flows with E810 VF, but can with E8= 10 PF
Product DPDK
Version 23.03
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component ethdev
Assignee dev@dpdk.org
Reporter maxime.leroy@6wind.com
Target Milestone --- 

Environnement
-------------

distribution for host/vm: Ubuntu 22.04.2 LTS, kernel 5.15.0-67-generic
kernel driver: 1.10.1.2.2
firmware-version: 4.10 0x80015191 1.3310.0
COMMS DDP: 1.3.37
ICE OS Default Package version 1.3.30.0
testpmd cmdline: ./build/app/dpdk-testpmd --log-level=3D.*ice.*,debug
--legacy-mem -c 7 -a 17:00.0 -a 0000:17:00.1  --  -i --nb-cores=3D2 --nb-po=
rts=3D2
--total-num-mbufs=3D2048
dpdk version: 23.03.0-rc4
NIC: Intel Corporation Ethernet Controller E810-C for QSFP=20

With PF (ice pmd)
-----------------

Working case, no sriov, no VM.=20

ICE PMD is able to create the following flows:

./build/app/dpdk-testpmd --log-level=3D.*ice.*,debug --legacy-mem -c 7 -a 1=
7:00.0
-a 0000:17:00.1  --  -i --nb-cores=3D2 --nb-ports=3D2 --total-num-mbufs=3D2=
048
testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1  / end acti=
ons
queue index 0 / end
ice_flow_create(): Succeeded to create (2) flow
Flow rule #0 created
testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end=
=20
actions queue index 0 / end
ice_flow_create(): Succeeded to create (2) flow
Flow rule #1 created


With VF (iavf pmd)
------------------

No working case sriov with a VM on the same device/hardware.

sriov devices:
 On PF : echo 1 > "/sys/bus/pci/devices/0000:17:00.0/sriov_numvfs&q=
uot; -> for VF
17.01.0
 On PF : echo 1 > "/sys/bus/pci/devices/0000:17:00.1/sriov_numvfs&q=
uot; -> for VF
17.11.0

QEMU ARGS: -device vfio-pci,host=3D0000:17:01.0,addr=3D04 -device
vfio-pci,host=3D0000:17:11.0,addr=3D05=20


./build/app/dpdk-testpmd --log-level=3D.*iavf.*,debug -c 0x6   -a 0000:00:0=
4.0 -a
0000:00:05.0   --  -i  --total-num-mbufs=3D2048
testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1  / end acti=
ons
queue index 0 / end
iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 47
iavf_fdir_add(): Succeed in adding rule request by PF
iavf_flow_create(): Succeeded to create (2) flow
Flow rule #0 created
testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end=
=20
actions queue index 0 / end
iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 47
iavf_fdir_add(): Failed to add rule request due to the rule is conflict with
existing rule
iavf_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Failed =
to
create parser engine.: Invalid argument

Conclusion
----------
IAVF is not able to create the second flow. Because the kernel driver
1.10.1.2.2 rejects the creation of second flow. There are no such issue with
ICE pmd of dpdk 23.03.0-rc4.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16801731590.Fa0aafe.3218854--