From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Yahui Cao <yahui.cao@intel.com>
Cc: Qiming Yang <qiming.yang@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>,
Beilei Xing <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] fix testpmd quit error after FDIR rule created
Date: Tue, 19 Nov 2019 13:11:33 +0800 [thread overview]
Message-ID: <20191119051133.GJ69793@intel.com> (raw)
In-Reply-To: <20191118222343.45282-1-yahui.cao@intel.com>
On 11/19, Yahui Cao wrote:
>This patch series fixes FDIR error when immediately quit without
>flushing FDIR rule in testpmd.
>
>- Patch 1 adds programming status check mechanism to monitor FDIR status.
>- Patch 2 moves FDIR queue irq config out of device start/stop.
>
>--
>v2:
>* Seperate FDIR/LAN queue irq config
>
>Yahui Cao (2):
> net/ice: fix FDIR programming status check issue
> net/ice: fix FDIR rule failure after device stop
>
> drivers/net/ice/ice_ethdev.c | 15 +----
> drivers/net/ice/ice_ethdev.h | 3 +
> drivers/net/ice/ice_fdir_filter.c | 7 +++
> drivers/net/ice/ice_rxtx.c | 93 +++++++++++++++++++++++++++++--
> 4 files changed, 100 insertions(+), 18 deletions(-)
>
>--
>2.17.1
>
Applied to dpdk-next-net-intel, Thanks.
prev parent reply other threads:[~2019-11-19 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 16:09 [dpdk-dev] [PATCH] net/ice: fix FDIR programming status check issue Yahui Cao
2019-11-14 7:23 ` Ye Xiaolong
2019-11-15 9:06 ` Ferruh Yigit
2019-11-18 22:23 ` [dpdk-dev] [PATCH v2 0/2] fix testpmd quit error after FDIR rule created Yahui Cao
2019-11-18 22:23 ` [dpdk-dev] [PATCH v2 1/2] net/ice: fix FDIR programming status check issue Yahui Cao
2019-11-18 22:23 ` [dpdk-dev] [PATCH v2 2/2] net/ice: fix FDIR rule failure after device stop Yahui Cao
2019-11-19 1:14 ` [dpdk-dev] [PATCH v2 0/2] fix testpmd quit error after FDIR rule created Zhang, Qi Z
2019-11-19 5:11 ` Ye Xiaolong [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=20191119051133.GJ69793@intel.com \
--to=xiaolong.ye@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yahui.cao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.