DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Leyi Rong <leyi.rong@intel.com>
Cc: wenzhuo.lu@intel.com, qi.z.zhang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] net/iavf: enable AVX2 for iavf
Date: Mon, 30 Sep 2019 17:47:20 +0800	[thread overview]
Message-ID: <20190930094720.GE112560@intel.com> (raw)
In-Reply-To: <20190923060257.86135-1-leyi.rong@intel.com>

On 09/23, Leyi Rong wrote:
>This patch enables AVX data path for iavf PMD.
>
>Signed-off-by: Leyi Rong <leyi.rong@intel.com>
>
>---
>v4:
>- Romoves redundant IAVF_NO_VECTOR_FLAGS define.
>
>v3:
>- Adds release note.
>
>v2:
>- Fixes build error on aarch64.
>---
> doc/guides/rel_notes/release_19_11.rst  |   3 +
> drivers/net/iavf/Makefile               |  21 +
> drivers/net/iavf/iavf_rxtx.c            |  99 +--
> drivers/net/iavf/iavf_rxtx.h            |  12 +
> drivers/net/iavf/iavf_rxtx_vec_avx2.c   | 867 ++++++++++++++++++++++++
> drivers/net/iavf/iavf_rxtx_vec_common.h |  65 ++
> drivers/net/iavf/iavf_rxtx_vec_sse.c    |  33 +
> drivers/net/iavf/meson.build            |  17 +
> 8 files changed, 1071 insertions(+), 46 deletions(-)
> create mode 100644 drivers/net/iavf/iavf_rxtx_vec_avx2.c
>

Applied to dpdk-next-net-intel.

  parent reply	other threads:[~2019-09-30  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 10:06 [dpdk-dev] [PATCH] " Leyi Rong
2019-09-04 13:29 ` Aaron Conole
2019-09-06  3:28 ` [dpdk-dev] [PATCH v2] " Leyi Rong
2019-09-19  8:44 ` [dpdk-dev] [PATCH v3] " Leyi Rong
2019-09-19 12:55   ` Zhang, Qi Z
2019-09-23  6:02 ` [dpdk-dev] [PATCH v4] " Leyi Rong
2019-09-23  6:49   ` Zhang, Qi Z
2019-09-30  9:47   ` Ye Xiaolong [this message]
2019-09-30 13:08   ` Ferruh Yigit
2019-10-16  8:14 ` [dpdk-dev] [PATCH v5] " Leyi Rong
2019-10-20  1:12   ` 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=20190930094720.GE112560@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=leyi.rong@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).