From: Bruce Richardson <bruce.richardson@intel.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: <dev@dpdk.org>, <kai.ji@intel.com>, <anatoly.burakov@intel.com>,
<qi.z.zhang@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH v2] net/ice: fix how ice driver handles flows
Date: Fri, 31 Jan 2025 11:45:39 +0000 [thread overview]
Message-ID: <Z5y349sJbJpsWkD-@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250130161442.2730917-1-vladimir.medvedkin@intel.com>
On Thu, Jan 30, 2025 at 04:14:42PM +0000, Vladimir Medvedkin wrote:
> Currently ICE PMD uses group attribute to select the appropriate HW engine
> to offload the flow. This behavior violates the rte_flow API, existing
> documentation/examples, and reveals hardware specific details.
>
> This patch eliminates the use of the group attribute and runs each engine
> parser in the order they work in the HW pipeline.
>
> Fixes: 9c5f0070fa3f ("net/ice: map group to pipeline stage")
> Cc: qi.z.zhang@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-net-intel,
Thanks,
/Bruce
PS: for future reference, minor feedback inline below.
> ---
> drivers/net/intel/ice/ice_generic_flow.c | 30 ++++++++++++++----------
> 1 file changed, 17 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/net/intel/ice/ice_generic_flow.c b/drivers/net/intel/ice/ice_generic_flow.c
> index 50d760004f..5c34e0385f 100644
> --- a/drivers/net/intel/ice/ice_generic_flow.c
> +++ b/drivers/net/intel/ice/ice_generic_flow.c
> @@ -20,6 +20,8 @@
>
> #define ICE_FLOW_ENGINE_DISABLED(mask, type) ((mask) & BIT(type))
>
> +#define ICE_FLOW_ENGINE_NB 3
> +
> static struct ice_engine_list engine_list =
> TAILQ_HEAD_INITIALIZER(engine_list);
>
> @@ -2295,21 +2297,23 @@ ice_flow_process_filter(struct rte_eth_dev *dev,
> return 0;
> }
>
> - parser = get_flow_parser(attr->group);
> - if (parser == NULL) {
> - rte_flow_error_set(error, EINVAL,
> - RTE_FLOW_ERROR_TYPE_ATTR,
> - NULL, "NULL attribute.");
> - return -rte_errno;
> - }
> + for (int i = 0; i < ICE_FLOW_ENGINE_NB; i++) {
> + parser = get_flow_parser(i);
> + if (parser == NULL) {
> + rte_flow_error_set(error, EINVAL,
> + RTE_FLOW_ERROR_TYPE_ATTR,
> + NULL, "NULL attribute.");
Since we allow up to 100 chars per line, this can be kept on two lines if
you want.
> + return -rte_errno;
> + }
>
> - if (ice_parse_engine(ad, flow, parser, attr->priority,
> - pattern, actions, error)) {
> - *engine = parser->engine;
> - return 0;
> - } else {
> - return -rte_errno;
> + if (ice_parse_engine(ad, flow, parser, attr->priority,
> + pattern, actions, error)) {
Similarly here, there is no need to wrap this statement - it all fits in
100 chars.
> + *engine = parser->engine;
> + return 0;
> + }
> }
> +
> + return -rte_errno;
> }
>
> static int
> --
> 2.43.0
>
prev parent reply other threads:[~2025-01-31 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 15:50 [PATCH] " Vladimir Medvedkin
2025-01-30 16:14 ` [PATCH v2] " Vladimir Medvedkin
2025-01-30 17:54 ` Bruce Richardson
2025-01-30 20:18 ` Medvedkin, Vladimir
2025-01-31 11:45 ` Bruce Richardson [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=Z5y349sJbJpsWkD-@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@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).