> -----Original Message-----
> From: Rong, Leyi <leyi.r...@intel.com>
> Sent: Wednesday, September 16, 2020 2:30 PM
> To: Jiang, JunyuX <junyux.ji...@intel.com>; dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zh...@intel.com>; Yang, Qiming
> <qiming.y...@intel.com>; Sun, GuinanX <guinanx....@intel.com>
> Subject: RE: [PATCH v3 0/5] supports RxDID #22 and FDID
> 
> 
> > -----Original Message-----
> > From: Jiang, JunyuX <junyux.ji...@intel.com>
> > Sent: Wednesday, September 16, 2020 11:10 AM
> > To: dev@dpdk.org
> > Cc: Rong, Leyi <leyi.r...@intel.com>; Zhang, Qi Z
> > <qi.z.zh...@intel.com>; Yang, Qiming <qiming.y...@intel.com>; Sun,
> > GuinanX <guinanx....@intel.com>; Jiang, JunyuX
> > <junyux.ji...@intel.com>
> > Subject: [PATCH v3 0/5] supports RxDID #22 and FDID
> >
> > This patchset supports flex Rx descriptor RxDID #22 and FDID offload in
> vPMD.
> > Remove devargs "flow-mark-support".
> >
> > ---
> > v3:
> > * Check if package does support RXDID.
> > * Modify commit message.
> > * Rebase the patchset.
> > v2:
> > * Reorder patches.
> >
> >
> > Guinan Sun (4):
> >   net/ice: add flow director enabled switch value
> >   net/ice: support flow mark in AVX path
> >   net/ice: support flow mark in SSE path
> >   net/ice: remove devargs flow-mark-support
> >
> > Junyu Jiang (1):
> >   net/ice: support flex Rx descriptor RxDID #22
> >
> >  doc/guides/nics/ice.rst               |  12 --
> >  drivers/net/ice/ice_ethdev.c          |  30 +++--
> >  drivers/net/ice/ice_ethdev.h          |   7 +-
> >  drivers/net/ice/ice_fdir_filter.c     |   9 +-
> >  drivers/net/ice/ice_rxtx.c            |  23 ++--
> >  drivers/net/ice/ice_rxtx.h            |  72 ++++++++++++
> >  drivers/net/ice/ice_rxtx_vec_avx2.c   | 162
> +++++++++++++++++++++++++-
> >  drivers/net/ice/ice_rxtx_vec_common.h |   6 -
> >  drivers/net/ice/ice_rxtx_vec_sse.c    | 138 +++++++++++++++++++---
> >  9 files changed, 402 insertions(+), 57 deletions(-)
> >
> > --
> > 2.17.1
> 
> 
> Acked-by: Leyi Rong <leyi.r...@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

Reply via email to