From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1204] ice: cannot create 2 rte_flows with MARK actions with dpdk 22.11.1, but can with dpdk 23.03.0-rc4
Date: Thu, 30 Mar 2023 09:00:10 +0000 [thread overview]
Message-ID: <bug-1204-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1204
Bug ID: 1204
Summary: ice: cannot create 2 rte_flows with MARK actions with
dpdk 22.11.1, but can with dpdk 23.03.0-rc4
Product: DPDK
Version: 22.11
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=.*ice.*,debug
--legacy-mem -c 7 -a 0000:17:00.0 -a 0000:17:00.1 -- -i --nb-cores=2
--nb-ports=2 --total-num-mbufs=2048
With dpdk 23.03.0-rc4
---------------------
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
actions mark id 1 / end
ice_flow_create(): Succeeded to create (2) flow
Flow rule #1 created
With dpdk 22.11.1
------------------
testpmd> flow create 0 ingress pattern eth / ipv4 proto is 1 / end actions
mark id 1 / 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 / end
ice_fdir_cross_prof_conflict(): Failed to create profile for flow type 1 due 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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3879 bytes --]
reply other threads:[~2023-03-30 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1204-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).