From: Ori Kam <orika@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: RE: [PATCH v2 3/7] ethdev: add flow rule insertion by index with pattern
Date: Thu, 26 Sep 2024 08:26:11 +0000 [thread overview]
Message-ID: <CH3PR12MB8257C9B87A0FB4EBFC5E1E13D66A2@CH3PR12MB8257.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240925180532.3958656-4-akozyrev@nvidia.com>
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, September 25, 2024 9:05 PM
>
> Add a new API to enqueue flow rule creation by index with pattern.
> The new template table rules insertion type,
> index-based insertion with pattern, requires a new flow rule creation
> function with both rule index and pattern provided.
> Packets will match on the provided pattern at the provided index.
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> ---
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
next prev parent reply other threads:[~2024-09-26 8:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 0:48 [PATCH 0/6] ethdev: jump to table support Alexander Kozyrev
2024-09-19 0:48 ` [PATCH 1/6] ethdev: add insertion by index with pattern Alexander Kozyrev
2024-09-25 15:01 ` Dariusz Sosnowski
2024-09-19 0:48 ` [PATCH 2/6] app/testpmd: add index with pattern insertion type Alexander Kozyrev
2024-09-25 15:01 ` Dariusz Sosnowski
2024-09-19 0:48 ` [PATCH 3/6] ethdev: add flow rule insertion by index with pattern Alexander Kozyrev
2024-09-25 15:00 ` Dariusz Sosnowski
2024-09-19 0:48 ` [PATCH 4/6] app/testpmd: add insertion by index with pattern option Alexander Kozyrev
2024-09-25 15:01 ` Dariusz Sosnowski
2024-09-19 0:48 ` [PATCH 5/6] ethdev: add jump to table index action Alexander Kozyrev
2024-09-25 15:01 ` Dariusz Sosnowski
2024-09-19 0:48 ` [PATCH 6/6] app/testpmd: " Alexander Kozyrev
2024-09-25 15:02 ` Dariusz Sosnowski
2024-09-25 18:05 ` [PATCH v2 0/7] ethdev: jump to table support Alexander Kozyrev
2024-09-25 18:05 ` [PATCH v2 1/7] ethdev: add insertion by index with pattern Alexander Kozyrev
2024-09-26 8:23 ` Ori Kam
2024-09-25 18:05 ` [PATCH v2 2/7] app/testpmd: add index with pattern insertion type Alexander Kozyrev
2024-09-26 8:24 ` Ori Kam
2024-09-25 18:05 ` [PATCH v2 3/7] ethdev: add flow rule insertion by index with pattern Alexander Kozyrev
2024-09-26 8:26 ` Ori Kam [this message]
2024-09-25 18:05 ` [PATCH v2 4/7] app/testpmd: add insertion by index with pattern option Alexander Kozyrev
2024-09-26 8:48 ` Ori Kam
2024-09-25 18:05 ` [PATCH v2 5/7] ethdev: add jump to table index action Alexander Kozyrev
2024-09-26 8:49 ` Ori Kam
2024-09-25 18:05 ` [PATCH v2 6/7] app/testpmd: " Alexander Kozyrev
2024-09-26 8:49 ` Ori Kam
2024-09-25 18:05 ` [PATCH v2 7/7] ethdev: add trace points to flow insertion by index Alexander Kozyrev
2024-09-26 8:50 ` Ori Kam
2024-09-25 19:28 ` [PATCH v2 0/7] ethdev: jump to table support Dariusz Sosnowski
2024-09-27 1:51 ` Ferruh Yigit
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=CH3PR12MB8257C9B87A0FB4EBFC5E1E13D66A2@CH3PR12MB8257.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=matan@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).