> -----Original Message-----
> From: Su, Simei <simei...@intel.com>
> Sent: Wednesday, April 15, 2020 10:55 AM
> To: Zhang, Qi Z <qi.z.zh...@intel.com>; Ye, Xiaolong
> <xiaolong...@intel.com>; Wu, Jingjing <jingjing...@intel.com>
> Cc: dev@dpdk.org; Cao, Yahui <yahui....@intel.com>; Su, Simei
> <simei...@intel.com>
> Subject: [PATCH v4 0/5] net/iavf: support FDIR capabiltiy
> 
> [PATCH v4 1/5] support FDIR common patterns and actions.
> [PATCH v4 2/5] support FDIR GTPU pattern.
> [PATCH v4 3/5] support FDIR L2TPv3, ESP, AH and NAT-T pattern.
> [PATCH v4 4/5] support FDIR PFCP node and session pattern.
> [PATCH v4 5/5] support FDIR mark action.
> 
> This patchset depend on the following patches on patchwork:
> https://patchwork.dpdk.org/cover/68372/
>     [v4,00/11] framework for advanced iAVF PMD
> 
> v4:
> * Add to check vf->vf_res.
> * Simplify some codes.
> * Specify and refine some error logs.
> 
> v3:
> * Add release notes.
> * Update action structures based on virtchnl update.
> * Add VIRTCHNL_FDIR_FAILURE_RULE_EXIST condition check and modify
>   the error log.
> 
> v2:
> * Update pattern and action structures based on latest virtchnl design.
> * Add upper bound check for pattern layers and action numbers.
> * Increase action number in mark only case.
> * Consider more circumstances about PF error return status.
> 
> Simei Su (5):
>   net/iavf: add support for FDIR basic rule
>   net/iavf: add support for FDIR GTPU
>   net/iavf: add support for FDIR L2TPv3 and IPSec
>   net/iavf: add support for FDIR PFCP
>   net/iavf: add support for FDIR mark action
> 
>  doc/guides/rel_notes/release_20_05.rst |   1 +
>  drivers/net/iavf/Makefile              |   1 +
>  drivers/net/iavf/iavf.h                |  18 +
>  drivers/net/iavf/iavf_fdir.c           | 971
> +++++++++++++++++++++++++++++++++
>  drivers/net/iavf/iavf_vchnl.c          | 154 +++++-
>  drivers/net/iavf/meson.build           |   1 +
>  6 files changed, 1145 insertions(+), 1 deletion(-)  create mode 100644
> drivers/net/iavf/iavf_fdir.c
> 
> --
> 1.8.3.1

Reviewed-by: Qi Zhang <qi.z.zh...@intel.com>


Reply via email to