From: "Li, Tao" <tao.li06@sap.com>
To: users <users@dpdk.org>
Subject: Failed to install synchronous rte flow rules to match IP in IP packets since DPDK 24.11.2
Date: Wed, 28 May 2025 08:04:28 +0000 [thread overview]
Message-ID: <AM0PR02MB5796FBDA1D83499BED1A07E88067A@AM0PR02MB5796.eurprd02.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Hello All,
We are running software components that use synchronous rte flow rules to match IP in IP packets. That means, we are matching packets with pattern of eth / ipv6 / ipv4 using rte flow rules. This approach works until DPDK 24.11.2. After investigation, we discover that, this patching commit [1] breaks matching of the above described header pattern, as it seems to only consider IP in IP tunneling coexisting with VXLAN encapsulation. To reproduce the error, the following testpmd commands can be used.
```
sudo ./dpdk-testpmd -a 0000:3b:00.0,class=rxq_cqe_comp_en=0,rx_vec_en=1,representor=pf[0]vf[0-3] -a 0000:3b:00.1,class=rxq_cqe_comp_en=0,rx_vec_en=1 -- -i --rxq=1 --txq=1 --flow-isolate-all
flow create 0 ingress pattern eth / ipv6 proto is 0x0004 / end actions queue index 0 / end
or
flow create 0 ingress pattern eth / ipv4 proto is 0x0004 / end actions queue index 0 / end
```
and the following error will be emitted:
```
port_flow_complain(): Caught PMD error type 13 (specific pattern item): cause: 0x7ffc9943af78, multiple tunnel not supported: Invalid argument
```
It would be appreciated to know if it is intended behavior or negative side effect of the mentioned DPDK patch commit. Would it be possible to again support IP in IP encapsulation for the outer headers?
[1] https://github.com/DPDK/dpdk-stable/commit/116949c7a7b780f147613068cbbd6257e6053654
Best regards,
Tao Li
[-- Attachment #2: Type: text/html, Size: 5722 bytes --]
reply other threads:[~2025-05-28 8:04 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=AM0PR02MB5796FBDA1D83499BED1A07E88067A@AM0PR02MB5796.eurprd02.prod.outlook.com \
--to=tao.li06@sap.com \
--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).