DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1 1/9] net/i40e: skip FDIR flow engine when FDIR is unavailable
Date: Fri, 30 Oct 2026 16:49:37 +0000	[thread overview]
Message-ID: <auTKoYngTHype9Fq@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <5e64cc416c8ab3b038eee6bb55836e0b8ed507ab.1793353214.git.anatoly.burakov@intel.com>

On Fri, Oct 30, 2026 at 09:40:14AM +0000, Anatoly Burakov wrote:
> The FDIR flow engine was initialized even when flow director was not
> usable. With no FDIR filter space, engine init failed and logged an
> error. When FDIR was disabled because its queue could not be allocated,
> the engine was initialized and FDIR flows only failed at install.
> 

This commit log is not entirely clear, for example, when you talk about cases
where the engine init already fails - given that you are adding code to
make the engine init fail.

> Return -ENOTSUP in both cases so that the engine is skipped.

You actually refer to 3 cases, I think: fdir not usable, no filter space,
and no queue allocation. From the patch, I don't see the third case being
relevant, so maybe drop the mention of it?

> 
> Fixes: 05432a6e4676 ("net/i40e: reimplement FDIR parser")
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>  drivers/net/intel/i40e/i40e_flow_fdir.c | 3 +++
>  1 file changed, 3 insertions(+)
> 

Code change looks reasonable, though, so with commit log cleanup:

Acked-by: Bruce Richardson <bruce.richardson@intel.com>


> diff --git a/drivers/net/intel/i40e/i40e_flow_fdir.c b/drivers/net/intel/i40e/i40e_flow_fdir.c
> index 55997295edb..197b93f3746 100644
> --- a/drivers/net/intel/i40e/i40e_flow_fdir.c
> +++ b/drivers/net/intel/i40e/i40e_flow_fdir.c
> @@ -2010,6 +2010,9 @@ i40e_fdir_flow_engine_init(const struct ci_flow_engine *engine,
>  	uint32_t i;
>  	int ret;
>  
> +	if ((pf->flags & I40E_FLAG_FDIR) == 0 || fdir_info->fdir_space_size == 0)
> +		return -ENOTSUP;
> +
>  	snprintf(fdir_hash_name, sizeof(fdir_hash_name), "fdir_%s", dev_data->name);
>  
>  	struct rte_hash_parameters fdir_hash_params = {
> -- 
> 2.52.0
> 

      parent reply	other threads:[~2026-10-30 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  9:40 [PATCH v1 1/9] net/i40e: skip FDIR flow engine when FDIR is unavailable Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 2/9] net/i40e: reject VLAN with tunnel items in FDIR flows Anatoly Burakov
2026-10-30 17:12   ` Bruce Richardson
2026-10-30  9:40 ` [PATCH v1 3/9] net/i40e: move FDIR flow state out of the flow engine Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 4/9] net/i40e: fix FDIR ethertype match with other items Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 5/9] net/i40e: validate IPv4 fragment offset without range Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 6/9] net/i40e: fix SCTP verification tag truncation in FDIR Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 7/9] net/i40e: validate raw FDIR offsets and lengths Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 8/9] net/i40e: disable tunnel replacement in multi-driver mode Anatoly Burakov
2026-10-30  9:40 ` [PATCH v1 9/9] net/i40e: allow L2 and L3 only hash patterns Anatoly Burakov
2026-10-30 16:49 ` 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=auTKoYngTHype9Fq@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    /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