DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix unexpected skip fdir setup
Date: Thu, 4 Jul 2019 02:17:47 +0000	[thread overview]
Message-ID: <94479800C636CB44BD422CB454846E013CE0163D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190703063449.23848-1-qi.z.zhang@intel.com>



> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Wednesday, July 3, 2019 2:35 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; stable@dpdk.org
> Subject: [PATCH] net/i40e: fix unexpected skip fdir setup
> 
> In i40e_flow_flush_fdir_filter, i40e_fdir_teardown is called, so
> i40e_fdir_setup is required to be called before create a new fdir flow.
> 
> Fixes: 2e67a7fbf3ff ("net/i40e: config flow director automatically")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
>  drivers/net/i40e/i40e_flow.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/i40e/i40e_flow.c b/drivers/net/i40e/i40e_flow.c index
> d62b32f17..48a6782a8 100644
> --- a/drivers/net/i40e/i40e_flow.c
> +++ b/drivers/net/i40e/i40e_flow.c
> @@ -3175,8 +3175,8 @@ i40e_flow_parse_fdir_filter(struct rte_eth_dev
> *dev,
> 
>  	cons_filter_type = RTE_ETH_FILTER_FDIR;
> 
> -	if (dev->data->dev_conf.fdir_conf.mode !=
> -	    RTE_FDIR_MODE_PERFECT) {
> +	if (dev->data->dev_conf.fdir_conf.mode !=
> RTE_FDIR_MODE_PERFECT ||
> +		pf->fdir.fdir_vsi == NULL) {
>  		/* Enable fdir when fdir flow is added at first time. */
>  		ret = i40e_fdir_setup(pf);
>  		if (ret != I40E_SUCCESS) {
> --
> 2.13.6

Acked-by: Beilei Xing <beilei.xing@intel.com>


  reply	other threads:[~2019-07-04  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  6:34 Qi Zhang
2019-07-04  2:17 ` Xing, Beilei [this message]
2019-07-05  1:14   ` Zhang, Qi Z

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=94479800C636CB44BD422CB454846E013CE0163D@SHSMSX101.ccr.corp.intel.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).