From: Stephen Hemminger <stephen@networkplumber.org>
To: Tony Hart <Tony.Hart@corero.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: rte_flow: no ability to match on packet length?
Date: Sun, 5 Mar 2023 12:46:28 -0800 [thread overview]
Message-ID: <20230305124628.503423b4@hermes.local> (raw)
In-Reply-To: <BLAPR10MB525263639AFC7419D9FCE2629EAC9@BLAPR10MB5252.namprd10.prod.outlook.com>
On Tue, 28 Feb 2023 15:12:31 +0000
Tony Hart <Tony.Hart@corero.com> wrote:
> I’m trying to use the Generic Flow API (rte_flow) to match IP packets based on their length (either L2, L3 or L4 lengths).
>
> There doesn’t seem to be an item type that explicitly matches based on length (RTE_FLOW_ITEM_TYPE_x). So I’ve tried using a mask with RTE_FLOW_ITEM_TYPE_IPV4 to match on the total_length field (and similar attempt to match on the UDP header dgram_len field) but the NIC I’m using (mlx5) returns an error (mask enables non supported bits).
>
> Am I out of luck, or maybe missing something?
>
> Thanks for any insights!
>
> I’ve tried, DPDK: 20.11.7 and 22.11.1
>
> Tony Hart | Chief Architect
> Tony.Hart@corero.com <mailto:Tony.Hart@corero.com>
Short answer: yes, you are right there is no generic length match.
Longer answer: rte_flow is an API which is meant to provide access to the underlying
match features of NIC hardware. Supporting something requires that the HW/FW can do the
match, and that the driver writer has added (and tested) that match.
Hopefully the MLX5 experts can help answer what is possible.
next prev parent reply other threads:[~2023-03-05 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5644d4d8-d47b-4a0c-84ec-17ce8d68d922.8b1a23e8-b9b9-4aca-a31a-0d4e4655acbd.eee7240b-6962-4037-97c6-178856ab054b@emailsignatures365.codetwo.com>
2023-02-28 15:12 ` Tony Hart
2023-03-05 20:46 ` Stephen Hemminger [this message]
2023-03-06 11:50 ` [External] " Tony Hart
2023-03-19 18:34 ` Asaf Penso
2023-03-21 9:57 ` Tony Hart
2023-03-21 13:00 ` Tony Hart
2023-03-21 16:49 ` Asaf Penso
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=20230305124628.503423b4@hermes.local \
--to=stephen@networkplumber.org \
--cc=Tony.Hart@corero.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).