DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Cao, Yahui" <yahui.cao@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Ye, Xiaolong" <xiaolong.ye@intel.com>,
	"Wang, Ying A" <ying.a.wang@intel.com>,
	"Su, Simei" <simei.su@intel.com>,
	"Sun, Chenmin" <chenmin.sun@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] fix FDIR support for GTPU
Date: Thu, 21 Nov 2019 03:58:47 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153DCE4C1@SHSMSX105.ccr.corp.intel.com> (raw)
In-Reply-To: <20191121112015.53711-1-yahui.cao@intel.com>



> -----Original Message-----
> From: Cao, Yahui <yahui.cao@intel.com>
> Sent: Thursday, November 21, 2019 7:20 PM
> To: Yang, Qiming <qiming.yang@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Cao, Yahui
> <yahui.cao@intel.com>; Ye, Xiaolong <xiaolong.ye@intel.com>; Wang, Ying A
> <ying.a.wang@intel.com>; Su, Simei <simei.su@intel.com>; Sun, Chenmin
> <chenmin.sun@intel.com>
> Subject: [PATCH v3 0/2] fix FDIR support for GTPU
> 
> This patch series enables FDIR support for both GTP-U and GTP-U with
> extension header.
> 
> - Patch 1 renames GTPU with extension header related variables
> - Patch 2 adds FDIR support for non-extension-header GTPU
> 
> --
> v3:
> * Change commit message
> 
> v2:
> * Re-organize patch
> 
> Yahui Cao (2):
>   net/ice: fix pattern name of GTPU with extension header
>   net/ice: add missing FDIR support for GTPU without extension header
> 
>  drivers/net/ice/ice_fdir_filter.c  | 10 ++++++++--
> drivers/net/ice/ice_generic_flow.c | 14 ++++++++++---
> drivers/net/ice/ice_generic_flow.h |  7 ++++---
>  drivers/net/ice/ice_hash.c         | 32 +++++++++++++++---------------
>  4 files changed, 39 insertions(+), 24 deletions(-)
> 
> --
> 2.17.1

Acked-by: Qi Zhang <qi.z.zhang@intel.com>


  reply	other threads:[~2019-11-21  3:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:28 [dpdk-dev] [PATCH 0/2] fix FDIR support for non-extension-header GTPU Yahui Cao
2019-11-20 13:28 ` [dpdk-dev] [PATCH 1/2] net/ice: fix GTPU and GTPU extension header mix Yahui Cao
2019-11-20 13:28 ` [dpdk-dev] [PATCH 2/2] net/ice: fix FDIR support for GTPU without extension header Yahui Cao
2019-11-20 15:05 ` [dpdk-dev] [PATCH v2 0/2] fix FDIR support for GTPU Yahui Cao
2019-11-20 15:05   ` [dpdk-dev] [PATCH v2 1/2] net/ice: fix GTPU extension header renaming Yahui Cao
2019-11-20  9:17     ` Zhang, Qi Z
2019-11-20 15:05   ` [dpdk-dev] [PATCH v2 2/2] net/ice: fix FDIR support for GTPU without extension header Yahui Cao
2019-11-20  9:18     ` Zhang, Qi Z
2019-11-21 11:20   ` [dpdk-dev] [PATCH v3 0/2] fix FDIR support for GTPU Yahui Cao
2019-11-21  3:58     ` Zhang, Qi Z [this message]
2019-11-21  5:27     ` Ye Xiaolong
2019-11-21 11:20     ` [dpdk-dev] [PATCH v3 1/2] net/ice: fix pattern name of GTPU with extension header Yahui Cao
2019-11-21 11:20     ` [dpdk-dev] [PATCH v3 2/2] net/ice: add missing FDIR support for GTPU without " Yahui Cao

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=039ED4275CED7440929022BC67E7061153DCE4C1@SHSMSX105.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=chenmin.sun@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=simei.su@intel.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xiaolong.ye@intel.com \
    --cc=yahui.cao@intel.com \
    --cc=ying.a.wang@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).