DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ergin, Mesut A" <mesut.a.ergin@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] net/i40e: add FDIR ID to vector rx
Date: Thu, 10 Oct 2019 00:02:14 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153DAC803@SHSMSX105.ccr.corp.intel.com> (raw)
In-Reply-To: <20191009152006.5768-1-harry.van.haaren@intel.com>



> -----Original Message-----
> From: Van Haaren, Harry
> Sent: Wednesday, October 9, 2019 11:20 PM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Ergin, Mesut A
> <mesut.a.ergin@intel.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>
> Subject: [PATCH v2 0/3] net/i40e: add FDIR ID to vector rx
> 
> v2:
> - Improve RSS clearning in SSE 16B descriptor
> - Fix AVX 16B descriptor data handling
> 
> ---
> 
> Hey All,
> 
> This series adds FDIR ID support to the vector Rx routines.
> Support for both the SSE and AVX drivers is added, and both the 16 byte and
> 32 byte descriptors are implemented.
> 
> A v1/RFC for this functionality was sent in 19.08 timeframe, refer to the
> patch as archived on patchwork here:
> http://patches.dpdk.org/patch/53969/
> 
> Regards, -Harry
> 
> Harry van Haaren (3):
>   net/i40e: cache fdir enable value in rx queue
>   net/i40e: add flow mark capability to SSE vector routine
>   net/i40e: add flow director support to avx rx path
> 
>  drivers/net/i40e/i40e_ethdev.h        |   1 +
>  drivers/net/i40e/i40e_fdir.c          |  20 +++
>  drivers/net/i40e/i40e_flow.c          |   4 +
>  drivers/net/i40e/i40e_rxtx.c          |   6 -
>  drivers/net/i40e/i40e_rxtx.h          |   8 ++
>  drivers/net/i40e/i40e_rxtx_vec_avx2.c | 193
> +++++++++++++++++++++++++-  drivers/net/i40e/i40e_rxtx_vec_sse.c  |
> 154 ++++++++++++++++++--
>  7 files changed, 367 insertions(+), 19 deletions(-)
> 
> --
> 2.17.1

Thanks for enabling this!
Acked-by: Qi Zhang <qi.z.zhang@intel.com>

  parent reply	other threads:[~2019-10-10  0:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  9:07 [dpdk-dev] [PATCH " Harry van Haaren
2019-10-07  9:07 ` [dpdk-dev] [PATCH 1/3] net/i40e: cache fdir enable value in rx queue Harry van Haaren
2019-10-07  9:07 ` [dpdk-dev] [PATCH 2/3] net/i40e: add flow mark capability to SSE vector routine Harry van Haaren
2019-10-07  9:07 ` [dpdk-dev] [PATCH 3/3] net/i40e: add flow director support to avx rx path Harry van Haaren
2019-10-09 15:20 ` [dpdk-dev] [PATCH v2 0/3] net/i40e: add FDIR ID to vector rx Harry van Haaren
2019-10-09 15:20   ` [dpdk-dev] [PATCH v2 1/3] net/i40e: cache fdir enable value in rx queue Harry van Haaren
2019-10-09 15:20   ` [dpdk-dev] [PATCH v2 2/3] net/i40e: add flow mark capability to SSE vector routine Harry van Haaren
2019-10-09 15:20   ` [dpdk-dev] [PATCH v2 3/3] net/i40e: add flow director support to avx rx path Harry van Haaren
2019-10-10  0:02   ` Zhang, Qi Z [this message]
2019-10-10 16:23     ` [dpdk-dev] [PATCH v2 0/3] net/i40e: add FDIR ID to vector rx Ergin, Mesut A
2019-10-21  6:04   ` Ye Xiaolong

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=039ED4275CED7440929022BC67E7061153DAC803@SHSMSX105.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=mesut.a.ergin@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).