From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/iavf: support generic flow
Date: Thu, 19 Mar 2020 02:01:18 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611547E3A07@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20200317081745.29450-2-qiming.yang@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Qiming Yang
> Sent: Tuesday, March 17, 2020 4:18 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>
> Subject: [dpdk-dev] [PATCH 1/2] net/iavf: support generic flow
>
> This patch added iavf_flow_create, iavf_flow_destroy, iavf_flow_flush and
> iavf_flow_validate support, these are used to handle all the generic filters.
>
> This patch supported basic L2, L3, L4 and GTPU patterns.
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
> doc/guides/rel_notes/release_20_05.rst | 5 +
> drivers/net/iavf/Makefile | 1 +
> drivers/net/iavf/iavf.h | 9 +
> drivers/net/iavf/iavf_ethdev.c | 46 ++
> drivers/net/iavf/iavf_generic_flow.c | 928
> +++++++++++++++++++++++++++++++++
> drivers/net/iavf/iavf_generic_flow.h | 279 ++++++++++
> drivers/net/iavf/meson.build | 1 +
> 7 files changed, 1269 insertions(+)
> create mode 100644 drivers/net/iavf/iavf_generic_flow.c
> create mode 100644 drivers/net/iavf/iavf_generic_flow.h
>
> diff --git a/doc/guides/rel_notes/release_20_05.rst
> b/doc/guides/rel_notes/release_20_05.rst
> index 2190eaf..44d375a 100644
> --- a/doc/guides/rel_notes/release_20_05.rst
> +++ b/doc/guides/rel_notes/release_20_05.rst
> @@ -56,6 +56,11 @@ New Features
> Also, make sure to start the actual text at the margin.
>
> =========================================================
>
> +* **Updated the Intel ice driver.**
> +
> + Updated the Intel ice driver with new features and improvements,
> including:
> +
> + * Added support for DCF (Device Config Function) feature.
Above comment is not related with this patch, right?
>
> Removed Items
> -------------
....
> +
> +static struct iavf_flow_engine *
> +iavf_parse_engine_create(struct iavf_adapter *ad,
> + struct rte_flow *flow,
> + struct iavf_parser_list *parser_list,
> + const struct rte_flow_item pattern[],
> + const struct rte_flow_action actions[],
> + struct rte_flow_error *error)
> +{
> + struct iavf_flow_engine *engine = NULL;
> + struct iavf_flow_parser_node *parser_node;
> + void *temp;
> + void *meta = NULL;
> +
> + TAILQ_FOREACH_SAFE(parser_node, parser_list, node, temp) {
> + if (parser_node->parser->parse_pattern_action(ad,
> + parser_node->parser->array,
> + parser_node->parser->array_len,
> + pattern, actions, &meta, error) < 0)
> + continue;
> +
> + engine = parser_node->parser->engine;
> + if (engine->create == NULL) {
> + rte_flow_error_set(error, EINVAL,
> + RTE_FLOW_ERROR_TYPE_HANDLE,
> + NULL, "Invalid engine");
> + continue;
> + }
Please sync with below fix for ice
https://patchwork.dpdk.org/patch/66232/
> +
> + if (!(engine->create(ad, flow, meta, error)))
> + return engine;
> + }
> + return NULL;
> +}
> +
> +static struct iavf_flow_engine *
> +iavf_parse_engine_validate(struct iavf_adapter *ad,
> + struct rte_flow *flow,
> + struct iavf_parser_list *parser_list,
> + const struct rte_flow_item pattern[],
> + const struct rte_flow_action actions[],
> + struct rte_flow_error *error)
> +{
> + struct iavf_flow_engine *engine = NULL;
> + struct iavf_flow_parser_node *parser_node;
> + void *temp;
> + void *meta = NULL;
> +
> + TAILQ_FOREACH_SAFE(parser_node, parser_list, node, temp) {
> + if (parser_node->parser->parse_pattern_action(ad,
> + parser_node->parser->array,
> + parser_node->parser->array_len,
> + pattern, actions, &meta, error) < 0)
> + continue;
> +
Please sync with below fix for ice
https://patchwork.dpdk.org/patch/66232/
> + engine = parser_node->parser->engine;
> + if (engine->validation == NULL) {
> + rte_flow_error_set(error, EINVAL,
> + RTE_FLOW_ERROR_TYPE_HANDLE,
> + NULL, "Validation not support");
> + continue;
> + }
next prev parent reply other threads:[~2020-03-19 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 8:17 [dpdk-dev] [PATCH 0/2] add generic filter support for iavf Qiming Yang
2020-03-17 8:17 ` [dpdk-dev] [PATCH 1/2] net/iavf: support generic flow Qiming Yang
2020-03-19 2:01 ` Zhang, Qi Z [this message]
2020-03-20 1:20 ` Yang, Qiming
2020-03-17 8:17 ` [dpdk-dev] [PATCH 2/2] net/iavf: support more patterns Qiming Yang
2020-03-30 8:30 ` [dpdk-dev] [PATCH v2 0/2] add generic filter support for iavf Qiming Yang
2020-03-30 8:30 ` [dpdk-dev] [PATCH v2 1/2] net/iavf: support generic flow Qiming Yang
2020-04-01 2:48 ` Zhang, Qi Z
2020-03-30 8:30 ` [dpdk-dev] [PATCH v2 2/2] net/iavf: support more patterns Qiming Yang
2020-04-03 5:42 ` [dpdk-dev] [PATCH v3 0/2] add generic filter support for iavf Qiming Yang
2020-04-03 5:42 ` [dpdk-dev] [PATCH v3 1/2] net/iavf: support generic flow Qiming Yang
2020-04-03 5:42 ` [dpdk-dev] [PATCH v3 2/2] net/iavf: support more patterns Qiming Yang
2020-04-03 6:03 ` [dpdk-dev] [PATCH v3 0/2] add generic filter support for iavf Zhang, Qi Z
2020-04-09 5:02 ` Ye Xiaolong
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=039ED4275CED7440929022BC67E70611547E3A07@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@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).