From: "Adam Kiripolský" <Adam.Kiripolsky@cesnet.cz>
To: users@dpdk.org
Subject: DPDK v23.11+ issue with Intel ICE driver and rte_flow 'count' and 'mark' actions
Date: Fri, 24 Jan 2025 17:44:39 +0100 [thread overview]
Message-ID: <6861b45d-a8f2-4771-83ca-c47ba4313c5f@cesnet.cz> (raw)
Hello all,
Ita stumbled upon an issue with rte_flow 'count' and 'mark' actions on
DPDK version 23.11 and higher on Intel ice driver.
By the table at https://doc.dpdk.org/guides/nics/overview.html ice
driver should support these actions.
Specifications:
NIC version: E810-C, 2x100G
Firmware version: 4.7
Kernel Driver: 1.16.3
DDP: 1.3.39.1
DDP Comms 1.3.46.0
DPDK versions that did not accept the rules: 23.11, 24.11
Testpmd start: sudo dpdk-testpmd -a 0000:af:00.1
--log-level=pmd.net.ice.driver:8 --file-prefix=sad -l 0,1 -- --txq=4
--rxq=4 -i --disable-rss
input:
testpmd> flow create 0 ingress pattern eth / ipv4 dst is 159.58.1.0 src
is 195.168.1.0 / end actions count identifier 128 / drop / end
output:
ice_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7ffc0c519398, Invalid action type: Invalid argument
input:
testpmd> flow create 0 ingress pattern eth / ipv4 dst is 159.58.1.0 src
is 195.168.1.0 / end actions mark id 2 / drop / end
output:
ice_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 16 (specific action): cause:
0x7fffc6ce9648, Invalid action type: Invalid argument
However, on DPDK version 23.07 both rules are accepted without an issue.
Were these features deprecated? Alternatively, is there any workaround
for counting packets matched against a rule?
Thanks,
Adam.
next reply other threads:[~2025-01-24 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 16:44 Adam Kiripolský [this message]
2025-02-06 13:23 ` Vladimir Medvedkin
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=6861b45d-a8f2-4771-83ca-c47ba4313c5f@cesnet.cz \
--to=adam.kiripolsky@cesnet.cz \
--cc=users@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).