From: Asaf Penso <asafp@nvidia.com>
To: Vladimir Yesin <v.yesin@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: Feature request: MLX5 DPDK flow item type RAW support
Date: Sat, 26 Feb 2022 18:08:26 +0000 [thread overview]
Message-ID: <DM5PR1201MB2555307765FDED23148826AECD3F9@DM5PR1201MB2555.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAABc1p+MoUXAsgKn4zyifeUnbXwTMVonGv85Q5meJwB1bv8KzQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
Hello Vladimir,
Would you please elaborate more on your use case?
What exactly do you wish to match on?
Currently, there is no plan to implement the RAW item.
However, with Bluefield 2 DPU, we implemented the flex item, that can be useful for you.
Regards,
Asaf Penso
________________________________
From: Vladimir Yesin <v.yesin@gmail.com>
Sent: Friday, February 25, 2022 4:28:57 PM
To: users@dpdk.org <users@dpdk.org>
Subject: Feature request: MLX5 DPDK flow item type RAW support
Current DPDK 21.11 flow API does not support RTE_FLOW_ITEM_TYPE_RAW for MLX5.
I need support of RTE_FLOW_ITEM_TYPE_RAW in DPDK flow API to enqueue some ingress packets by content to GPU with support of GPUDirect RDMA and other to CPU via distinct HW queues (RTE_FLOW_ACTION_TYPE_QUEUE).
For now RTE_FLOW_ITEM_TYPE_UDP and RTE_FLOW_ITEM_TYPE_IPV4 filtering and enqueueing with address and ports are supported.
Are there any plans to support RTE_FLOW_ITEM_TYPE_RAW for MLX5?
[-- Attachment #2: Type: text/html, Size: 2173 bytes --]
next prev parent reply other threads:[~2022-02-26 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 14:28 Vladimir Yesin
2022-02-26 18:08 ` Asaf Penso [this message]
2022-03-01 8:01 ` Vladimir Yesin
2022-03-02 19:26 ` 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=DM5PR1201MB2555307765FDED23148826AECD3F9@DM5PR1201MB2555.namprd12.prod.outlook.com \
--to=asafp@nvidia.com \
--cc=users@dpdk.org \
--cc=v.yesin@gmail.com \
/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).