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 v5] net/iavf: enable AVX2 for iavf
Date: Sun, 20 Oct 2019 09:12:15 +0800 [thread overview]
Message-ID: <20191020011215.GB108019@intel.com> (raw)
In-Reply-To: <20191016081409.10903-1-leyi.rong@intel.com>
On 10/16, Leyi Rong wrote:
>This patch enables AVX data path for iavf PMD.
>
>Signed-off-by: Leyi Rong <leyi.rong@intel.com>
>
>---
>v5:
>- Eliminates CONFIG_RTE_LIBRTE_IAVF_INC_VECTOR and __rte_weak.
>
>v4:
>- Romoves redundant IAVF_NO_VECTOR_FLAGS define.
>
>v3:
>- Adds release note.
>
>v2:
>- Fixes build error on aarch64.
>---
> config/common_base | 1 -
> doc/guides/rel_notes/release_19_11.rst | 4 +
> drivers/net/iavf/Makefile | 23 +-
> drivers/net/iavf/iavf_ethdev.c | 5 -
> drivers/net/iavf/iavf_rxtx.c | 141 ++--
> 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 | 18 +-
> 10 files changed, 1074 insertions(+), 95 deletions(-)
> create mode 100644 drivers/net/iavf/iavf_rxtx_vec_avx2.c
>
Applied to dpdk-next-net-intel.
Thanks,
Xiaolong
prev parent reply other threads:[~2019-10-20 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 10:06 [dpdk-dev] [PATCH] net/iavf: enable AVX2 for iavf 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
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 [this message]
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=20191020011215.GB108019@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.