DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Liu, Lingyu" <lingyu.liu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/i40e: clear FDIR SW input set when destroy rules
Date: Tue, 15 Jun 2021 08:36:05 +0000	[thread overview]
Message-ID: <MN2PR11MB3807B31B345EE7F653BD1224F7309@MN2PR11MB3807.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210615145259.51859-1-lingyu.liu@intel.com>



> -----Original Message-----
> From: Liu, Lingyu <lingyu.liu@intel.com>
> Sent: Tuesday, June 15, 2021 10:53 PM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>
> Cc: Liu, Lingyu <lingyu.liu@intel.com>
> Subject: [PATCH v1] net/i40e: clear FDIR SW input set when destroy rules
> 
> When a FDIR rule is destroyed, the corresponding input set needs to be
> cleared.
> 
The fix should be if deleting all the rules of some PCTYPE, then the input set need to reset.

Missed fix line.

> Signed-off-by: Lingyu Liu <lingyu.liu@intel.com>
> ---
>  drivers/net/i40e/i40e_fdir.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/net/i40e/i40e_fdir.c b/drivers/net/i40e/i40e_fdir.c index
> ac0e09bfdd..e679324c20 100644
> --- a/drivers/net/i40e/i40e_fdir.c
> +++ b/drivers/net/i40e/i40e_fdir.c
> @@ -1845,6 +1845,10 @@ i40e_flow_add_del_fdir_filter(struct rte_eth_dev
> *dev,
>  			return -EINVAL;
>  		}
> 
> +		/* clear input_set flag */
> +		pf->fdir.input_set[pctype] = 0;
> +		pf->fdir.inset_flag[pctype] = 0;
> +

So should check if it's the last rule of the pctype.

>  		pf->fdir.flex_mask_flag[pctype] = 0;
> 
>  		if (fdir_info->fdir_invalprio == 1)
> --
> 2.25.1


      reply	other threads:[~2021-06-15  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 14:52 Lingyu Liu
2021-06-15  8:36 ` Xing, Beilei [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=MN2PR11MB3807B31B345EE7F653BD1224F7309@MN2PR11MB3807.namprd11.prod.outlook.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=lingyu.liu@intel.com \
    --cc=qi.z.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).