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 A01BA42850; Thu, 30 Mar 2023 10:54:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8676A410D3; Thu, 30 Mar 2023 10:54:01 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 4543840E25 for ; Thu, 30 Mar 2023 10:54:00 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 3689A42861; Thu, 30 Mar 2023 10:54:00 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1203] ice: cannot create 2 rte_flows with 2 actions, only with 1 action Date: Thu, 30 Mar 2023 08:54: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=16801664400.d608b7.3202948 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 --16801664400.d608b7.3202948 Date: Thu, 30 Mar 2023 10:54:00 +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=3D1203 Bug ID: 1203 Summary: ice: cannot create 2 rte_flows with 2 actions, only with 1 action 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: --- 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 RTE_FLOWS rules can be created ------------------------------ With queue action: 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 mark action: testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions mark id 1 / 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 mark id 1 / end ice_flow_create(): Succeeded to create (2) flow Flow rule #1 created RTE_FLOWS rules cannot be created --------------------------------- with mark + queue action: testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions mark id 1 / queue index 0 / end ice_fdir_rx_parsing_enable(): FDIR processing on RX set to 1 ice_flow_create(): Succeeded to create (1) flow Flow rule #0 created testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end act= ions mark id 1 / queue index 0 / end ice_fdir_cross_prof_conflict(): Failed to create profile for flow type 1 du= e to conflict with existing rule of flow type 4. ice_flow_create(): Failed to create flow port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Profile configure failed.: Invalid argument with mark + passthru action: testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions mark id 1 / passthru / end ice_fdir_rx_parsing_enable(): FDIR processing on RX set to 1 ice_flow_create(): Succeeded to create (1) flow Flow rule #0 created testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end act= ions mark id 1 / passthru / end ice_fdir_cross_prof_conflict(): Failed to create profile for flow type 1 du= e to conflict with existing rule of flow type 4. ice_flow_create(): Failed to create flow port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Profile configure failed.: Invalid argument Question -------- 1. Does ice nics support to have several actions ? 2. What is the difference between MARK vs MARK+PASSTRHU ? It seems to be the same: http://git.dpdk.org/dpdk/commit/?id=3D0f664f7d57268f9ab9bdef95f0d48b3ce5= 004a61 In this case, there is no reason to support MARK and not MARK+PASSTRHU w= ith 2 flows. --=20 You are receiving this mail because: You are the assignee for the bug.= --16801664400.d608b7.3202948 Date: Thu, 30 Mar 2023 10:54:00 +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 1203
Summary ice: cannot create 2 rte_flows with 2 actions, only with 1 ac= tion
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 --- 

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


RTE_FLOWS rules can be created
------------------------------


With queue action:

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 mark action:

testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1  / end acti=
ons
mark id 1 / 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 mark id 1 / end
ice_flow_create(): Succeeded to create (2) flow
Flow rule #1 created

RTE_FLOWS rules cannot be created
---------------------------------

with mark + queue action:

testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1  / end acti=
ons
mark id 1 / queue index 0 / end
ice_fdir_rx_parsing_enable(): FDIR processing on RX set to 1
ice_flow_create(): Succeeded to create (1) flow
Flow rule #0 created
testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end =
actions
 mark id 1 / queue index 0 / end
ice_fdir_cross_prof_conflict(): Failed to create profile for flow type 1 du=
e to
conflict with existing rule of flow type 4.
ice_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Profile
configure failed.: Invalid argument

with mark + passthru action:

testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1  / end acti=
ons
mark id 1 / passthru / end
ice_fdir_rx_parsing_enable(): FDIR processing on RX set to 1
ice_flow_create(): Succeeded to create (1) flow
Flow rule #0 created
testpmd> flow create 0 ingress pattern eth / ipv4 / udp src is 22 / end =
actions
 mark id 1 / passthru / end
ice_fdir_cross_prof_conflict(): Failed to create profile for flow type 1 du=
e to
conflict with existing rule of flow type 4.
ice_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Profile
configure failed.: Invalid argument

Question
--------

1. Does ice nics support to have several actions ?
2. What is the difference between MARK vs MARK+PASSTRHU ?
   It seems to be the same:
   http://git.dpdk.org/dpdk/commit/?id=3D0f664f7d57268f9ab9=
bdef95f0d48b3ce5004a61
   In this case, there is no reason to support MARK and not MARK+PASSTRHU w=
ith
2   flows.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16801664400.d608b7.3202948--