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 473BFA0543; Sun, 18 Dec 2022 00:32:59 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3A0DB40A7A; Sun, 18 Dec 2022 00:32:59 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 017DF40685 for ; Sun, 18 Dec 2022 00:32:57 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id E4CA4A0545; Sun, 18 Dec 2022 00:32:57 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1154] RTE flow: Getting a conflict error even though the rules doesn't have a conflict Date: Sat, 17 Dec 2022 23:32:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 22.07 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lthammin@usc.edu 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: 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 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 https://bugs.dpdk.org/show_bug.cgi?id=3D1154 Bug ID: 1154 Summary: RTE flow: Getting a conflict error even though the rules doesn't have a conflict Product: DPDK Version: 22.07 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: other Assignee: dev@dpdk.org Reporter: lthammin@usc.edu Target Milestone: --- I am configuring below two flows on i40e through VPP and am seeing errors saying "Failed to create flow" and "i40e_flow_set_fdir_inset(): Conflict wi= th the first rule's input set" although I don't see any conflict between the flows. Other combinations work good say if protocol is not 'any' (wildcard). Let me know if I am doing it wrong or if it's a bug. The 2 flows are: 1. type/pattern: src-ip 1.1.1.1 dst-ip 2.2.2.2 protocol any action: redirect-to-queue 0 2. type/pattern: src-ip 3.3.3.3 dst-ip 4.4.4.4 protocol icmp action: redirect-to-queue 1 Logs: DBGvpp# sh int Name Idx State MTU (L3/IP4/IP6/MPLS)=20=20= =20=20 Counter Count TenGigabitEthernetb5/0/3 1 up 9000/0/0/0 local0 0 down 0/0/0/0 DBGvpp# DBGvpp# DBGvpp# test flow add src-ip 1.1.1.1 dst-ip 2.2.2.2 proto any redirect-to-q= ueue 0 flow 0 added DBGvpp# test flow add src-ip 3.3.3.3 dst-ip 4.4.4.4 proto icmp redirect-to-queue 1 flow 1 added DBGvpp# DBGvpp# sh flow entry flow-index 0 type ipv4 active 0 match: src_addr 1.1.1.1, dst_addr 2.2.2.2, protocol any action: redirect-to-queue redirect-to-queue 0 flow-index 1 type ipv4 active 0 match: src_addr 3.3.3.3, dst_addr 4.4.4.4, protocol ICMP action: redirect-to-queue redirect-to-queue 1 DBGvpp# DBGvpp# clear log DBGvpp# DBGvpp# test flow enable index 0 TenGigabitEthernetb5/0/3 DBGvpp# DBGvpp# show log DBGvpp# DBGvpp# show flow int TenGigabitEthernetb5/0/3 supported flow actions : count mark buffer-advance redirect-to-node redirect-to-queue rss drop last DPDK error type : 0 last DPDK error message : n/a DBGvpp# DBGvpp# test flow enable index 1 TenGigabitEthernetb5/0/3 test flow: flow error: "not supported" DBGvpp# DBGvpp# show flow int TenGigabitEthernetb5/0/3 supported flow actions : count mark buffer-advance redirect-to-node redirect-to-queue rss drop last DPDK error type : 2 last DPDK error message : Failed to create flow. DBGvpp# DBGvpp# show log 2022/12/17 23:13:47:439 notice dpdk i40e_flow_set_fdir_inset(= ): Conflict with the first rule's input set. DBGvpp# DBGvpp# Thanks, Nikhil --=20 You are receiving this mail because: You are the assignee for the bug.=