From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tomer Shmilovich <tshmilovich@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/2] ethdev: add group set miss actions API
Date: Fri, 29 Sep 2023 12:02:52 +0100 [thread overview]
Message-ID: <6edf8616-2310-472b-8b18-0acd45a69bdc@amd.com> (raw)
In-Reply-To: <20230920125250.804055-1-tshmilovich@nvidia.com>
On 9/20/2023 1:52 PM, Tomer Shmilovich wrote:
> Introduce new group set miss actions API:
> rte_flow_group_set_miss_actions().
>
> A group's miss actions are a set of actions to be performed
> in case of a miss on a group, i.e. when a packet didn't hit any flow
> rules in the group.
>
> Currently, the expected behavior in this case is undefined.
> In order to achieve such functionality, a user can add a flow rule
> that matches on all traffic with the lowest priority in the group -
> this is not explicit however, and can be overridden by another flow rule
> with a lower priority.
>
> This new API function allows a user to set a group's miss actions in an
> explicit way.
>
> RFC discussion: http://patches.dpdk.org/project/dpdk/patch/20230807133601.164018-1-tshmilovich@nvidia.com/
>
> Tomer Shmilovich (2):
> ethdev: add group set miss actions API
> app/testpmd: add group set miss actions CLI commands
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-09-29 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 12:52 Tomer Shmilovich
2023-09-20 12:52 ` [PATCH 1/2] " Tomer Shmilovich
2023-09-20 12:52 ` [PATCH 2/2] app/testpmd: add group set miss actions CLI commands Tomer Shmilovich
2023-09-29 11:02 ` Ferruh Yigit [this message]
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=6edf8616-2310-472b-8b18-0acd45a69bdc@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=tshmilovich@nvidia.com \
--cc=yuying.zhang@intel.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).