From: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
honnappa.nagarahalli@arm.com, juraj.linkes@pantheon.tech,
nd@arm.com, Ruifeng Wang <ruifeng.wang@arm.com>
Subject: [dpdk-dev] [PATCH v2 0/4] aarch32 compilation
Date: Tue, 23 Jun 2020 14:58:52 +0800 [thread overview]
Message-ID: <20200623065856.41189-1-ruifeng.wang@arm.com> (raw)
In-Reply-To: <20200424065053.119885-1-ruifeng.wang@arm.com>
Build aarch32 binary on aarch64 platform hit issues with l3fwd [1]
and ixgbe PMD [2]. This patch set is to fix these.
When building with make, please refer to guide:
http://patches.dpdk.org/patch/62820/
When building with meson, requires series:
http://patches.dpdk.org/cover/69536/
[1] https://mails.dpdk.org/archives/dev/2020-April/162673.html
[2] https://mails.dpdk.org/archives/dev/2020-April/163846.html
v2:
Fix aarch32 Make build for ixgbe, and enable ixgbe PMD by default.
Add aarch32 support for i40e, and enable i40e PMD by default.
Ruifeng Wang (4):
arch/arm: add vcopyq intrinsic for aarch32
net/ixgbe: add support for aarch32
net/ixgbe: fix include of vector header file
net/i40e: add support for aarch32
config/defconfig_arm-armv7a-linuxapp-gcc | 4 ++--
drivers/net/i40e/Makefile | 2 +-
drivers/net/i40e/i40e_rxtx_vec_neon.c | 2 +-
drivers/net/ixgbe/Makefile | 2 +-
drivers/net/ixgbe/ixgbe_rxtx.h | 4 ++--
drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c | 3 +--
lib/librte_eal/arm/include/rte_vect.h | 6 +++++-
7 files changed, 13 insertions(+), 10 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2020-06-23 6:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 6:50 [dpdk-dev] [PATCH 0/3] " Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 1/3] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-05-01 14:55 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-04-24 6:50 ` [dpdk-dev] [PATCH 2/3] net/ixgbe: add support " Ruifeng Wang
2020-05-01 14:59 ` Ferruh Yigit
2020-05-06 7:54 ` Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 3/3] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-05-01 15:06 ` [dpdk-dev] [PATCH 0/3] aarch32 compilation Ferruh Yigit
2020-05-06 8:09 ` Ruifeng Wang
2020-05-06 10:14 ` Ferruh Yigit
2020-05-06 13:54 ` Ruifeng Wang
2020-05-06 14:14 ` Ferruh Yigit
2020-05-06 14:36 ` Ruifeng Wang
2020-06-23 6:58 ` Ruifeng Wang [this message]
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-23 8:37 ` David Marchand
2020-06-23 8:59 ` Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-26 13:44 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ferruh Yigit
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=20200623065856.41189-1-ruifeng.wang@arm.com \
--to=ruifeng.wang@arm.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.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).