From: Yongseok Koh <yskoh@mellanox.com>
To: adrien.mazarguil@6wind.com, nelio.laranjeiro@6wind.com
Cc: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-dev] [RFC PATCH 0/1] net/mlx5: add vectorized Rx/Tx burst for ARM
Date: Fri, 25 Aug 2017 11:40:22 -0700 [thread overview]
Message-ID: <20170825184023.31692-1-yskoh@mellanox.com> (raw)
The SSE(x86) Rx/Tx burst functions added in v17.08 would be ported for ARM NEON
in v17.11. Although this is still ongoing effort (more implementation and
further optimization), this intrim patch can be applied on top of v17.08 and
forward packts.
One of topics to discuss is that I used inilne assembly for performance critical
code blocks because I don't think intrinsics for NEON aren't well optimized yet,
especially vqtbl2q_u8()/vqtbl3q_u8()/vqtbl4q_u8() and gcc's register
optimization. And older gcc doesn't even have vld1q_u8_x4(). I used it to get
rid of hotspots shown in profiling result. I'm not sure whether inline assembly
is allowed in DPDK community. But, I believe there's no reason to prohibit it.
In my patch, some of functions are commented out as I'm not done migrating those
yet. But this is functional (Rx/Tx). For Tx, "--txqflags=0xf01" is needed
because I haven't ported txq_scatter_v() yet.
Yongseok Koh (1):
net/mlx5: add vectorized Rx/Tx burst for ARM
drivers/net/mlx5/Makefile | 2 +
drivers/net/mlx5/mlx5_ethdev.c | 4 +-
drivers/net/mlx5/mlx5_prm.h | 15 +
drivers/net/mlx5/mlx5_rxq.c | 61 ++
drivers/net/mlx5/mlx5_rxtx.h | 3 +-
drivers/net/mlx5/mlx5_rxtx_vec_neon.c | 1464 +++++++++++++++++++++++++++++++++
6 files changed, 1546 insertions(+), 3 deletions(-)
create mode 100644 drivers/net/mlx5/mlx5_rxtx_vec_neon.c
--
2.11.0
next reply other threads:[~2017-08-25 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 18:40 Yongseok Koh [this message]
2017-08-25 18:40 ` [dpdk-dev] [RFC PATCH 1/1] " Yongseok Koh
2017-09-04 12:37 ` Nélio Laranjeiro
2017-09-11 23:28 ` Yongseok Koh
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=20170825184023.31692-1-yskoh@mellanox.com \
--to=yskoh@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.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).