From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gregory Etelson <getelson@nvidia.com>, <dev@dpdk.org>,
<viacheslavo@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>, Thomas Monjalon <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: fix variable length flow elements support
Date: Thu, 4 Nov 2021 12:46:29 +0000 [thread overview]
Message-ID: <f93db4b0-2dd8-99df-cb9b-255967b07e1f@intel.com> (raw)
In-Reply-To: <20211104112721.4025-1-getelson@nvidia.com>
On 11/4/2021 11:27 AM, Gregory Etelson wrote:
> RTE flow API defines two flow elements types - common and PMD private.
> Common RTE flow types are defined in rte_flow.h while PMD private
> types exists inside specific PMD only. Application can create a flow
> rule with PMD private items or actions. RTE flow API restricts
> private PMD types to negative values.
>
> Current implementation tried to use negative PMD private item type
> value as index in the rte_flow_desc_item[] array.
>
> The patch allows access to rte_flow_desc_item[] and
> rte_flow_desc_action[] arrays to non-private PMD types only.
>
> Fixes: 6cf72047332b ("ethdev: support flow elements with variable length")
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-04 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 9:05 [dpdk-dev] [PATCH] " Gregory Etelson
2021-11-03 21:04 ` Ferruh Yigit
2021-11-04 5:33 ` Gregory Etelson
2021-11-04 9:10 ` Ferruh Yigit
2021-11-04 9:20 ` Gregory Etelson
2021-11-04 11:27 ` [dpdk-dev] [PATCH v2] " Gregory Etelson
2021-11-04 12:46 ` 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=f93db4b0-2dd8-99df-cb9b-255967b07e1f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).