From: Asaf Penso <asafp@nvidia.com>
To: Tao Li <byteocean@hotmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: Finer matching granularity with async template API
Date: Thu, 21 Mar 2024 19:17:04 +0000 [thread overview]
Message-ID: <SA3PR12MB881179E6B7EC4556A24D7799CD322@SA3PR12MB8811.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DB9P193MB1739F96764E8CEEB53C3CFA3A3322@DB9P193MB1739.EURP193.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2999 bytes --]
Hello Tao,
What is the output / error message you get?
Regards,
Asaf Penso
________________________________
From: Tao Li <byteocean@hotmail.com>
Sent: Thursday, March 21, 2024 5:44:00 PM
To: users@dpdk.org <users@dpdk.org>
Subject: Finer matching granularity with async template API
Hi all,
I am using async template API to install flow rules to perform actions on packets to achieve IP(v4)inIP(v6) tunnelling. Currently I am facing an issue where I cannot perform incoming traffic matching with finer granularity. The test-pmd commands in use are as following:
<Not working test-pmd commands>
port stop all
flow configure 0 queues_number 4 queues_size 64 counters_number 0 aging_counters_number 0 meters_number 0 flags 0 # PF0
flow configure 1 queues_number 4 queues_size 64 counters_number 0 aging_counters_number 0 meters_number 0 flags 0
flow configure 2 queues_number 4 queues_size 64 counters_number 0 aging_counters_number 0 meters_number 0 flags 0
flow configure 3 queues_number 4 queues_size 64 counters_number 0 aging_counters_number 0 meters_number 0 flags 0 # PF1V0
port start all
set verbose 1
flow pattern_template 0 create transfer relaxed no pattern_template_id 10 template represented_port ethdev_port_id is 0 / eth / ipv6 / ipv4 / icmp / end
set raw_decap 0 eth / ipv6 / end_set
set raw_encap 0 eth src is 11:22:33:44:55:66 dst is 66:9d:a7:fd:fb:43 type is 0x0800 / end_set
flow actions_template 0 create transfer actions_template_id 10 template raw_decap index 0 / raw_encap index 0 / represented_port / end mask raw_decap index 0 / raw_encap index 0 / represented_port / end
flow template_table 0 create group 0 priority 0 transfer wire_orig table_id 5 rules_number 8 pattern_template 10 actions_template 10
flow queue 0 create 0 template_table 5 pattern_template 0 actions_template 0 postpone no pattern represented_port ethdev_port_id is 0 / eth / ipv6 / ipv4 / icmp / end actions raw_decap index 0 / raw_encap index 0 / represented_port ethdev_port_id 3 / end
flow push 0 queue 0
</Not working test-pmd commands>
Once I remove matching patterns for the inner packet headers( ipv4 / icmp) as following, I can see the processed packets inside VMs using tcpdump.
<Working test-pmd commands>
…
flow pattern_template 0 create transfer relaxed no pattern_template_id 10 template represented_port ethdev_port_id is 0 / eth / ipv6 / end
…
flow queue 0 create 0 template_table 5 pattern_template 0 actions_template 0 postpone no pattern represented_port ethdev_port_id is 0 / eth / ipv6 / end actions raw_decap index 0 / raw_encap index 0 / represented_port ethdev_port_id 3 / end
…
</Working test-pmd commands>
Similar combination works when using the synchronous rte_flow API. Any comment or suggestion on this issue is much appreciated. Many thanks in advance.
Best regards,
Tao
[-- Attachment #2: Type: text/html, Size: 7644 bytes --]
next prev parent reply other threads:[~2024-03-21 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:44 Tao Li
2024-03-21 19:17 ` Asaf Penso [this message]
2024-03-21 19:18 ` Asaf Penso
2024-03-22 13:19 ` Tao Li
2024-03-22 15:08 ` Tao Li
2024-03-26 19:43 ` Asaf Penso
2024-04-03 10:06 ` Tao Li
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=SA3PR12MB881179E6B7EC4556A24D7799CD322@SA3PR12MB8811.namprd12.prod.outlook.com \
--to=asafp@nvidia.com \
--cc=byteocean@hotmail.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).