From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Sun, Chenmin" <chenmin.sun@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/i40e: fix fdir cannot receive rx writeback issue
Date: Fri, 17 Jul 2020 14:48:03 +0000 [thread overview]
Message-ID: <MN2PR11MB3807D6120E7D3CC7E5212664F77C0@MN2PR11MB3807.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200717145758.46368-1-chenmin.sun@intel.com>
> -----Original Message-----
> From: Sun, Chenmin <chenmin.sun@intel.com>
> Sent: Friday, July 17, 2020 10:58 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Sun, Chenmin <chenmin.sun@intel.com>
> Subject: [PATCH v3] net/i40e: fix fdir cannot receive rx writeback issue
>
> From: Chenmin Sun <chenmin.sun@intel.com>
>
> This patch fixes the fdir cannot receive rx writeback packet issue.
> The root cause is FDIR interrupt is not correctly enabled.
>
> Beside this, to make sure fdir programming works fine when the port is
> stopped, move the fdir interrupt configure from start/stop to setup/teardown.
>
> Fixes: cfd662d22e7b ("net/i40e: fix interrupt throttling setting in PF")
>
> Signed-off-by: Chenmin Sun <chenmin.sun@intel.com>
Acked-by: Beilei Xing <beilei.xing@intel.com>
next prev parent reply other threads:[~2020-07-17 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 22:48 [dpdk-dev] [PATCH] " chenmin.sun
2020-07-15 23:03 ` [dpdk-dev] [PATCH V2] " chenmin.sun
2020-07-16 8:25 ` Xing, Beilei
2020-07-17 14:57 ` [dpdk-dev] [PATCH v3] " chenmin.sun
2020-07-17 14:48 ` Xing, Beilei [this message]
2020-07-20 9:51 ` 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=MN2PR11MB3807D6120E7D3CC7E5212664F77C0@MN2PR11MB3807.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=chenmin.sun@intel.com \
--cc=dev@dpdk.org \
--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).