From: Stanislaw Kardach <kda@semihalf.com>
To: dev@dpdk.org
Cc: Stanislaw Kardach <kda@semihalf.com>,
Frank Zhao <Frank.Zhao@starfivetech.com>,
Sam Grove <sam.grove@sifive.com>,
mw@semihalf.com, upstream@semihalf.com
Subject: [PATCH RESEND v4 5/8] examples/l3fwd: enable RISC-V operation
Date: Tue, 7 Jun 2022 12:46:14 +0200 [thread overview]
Message-ID: <20220607104617.153892-6-kda@semihalf.com> (raw)
In-Reply-To: <20220607104617.153892-1-kda@semihalf.com>
Add missing em_mask_key() implementation and fix l3fwd_common.h
inclusion in FIB lookup functions to enable the l3fwd to be run on
RISC-V.
Sponsored-by: Frank Zhao <Frank.Zhao@starfivetech.com>
Sponsored-by: Sam Grove <sam.grove@sifive.com>
Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
---
examples/l3fwd/l3fwd_em.c | 8 ++++++++
examples/l3fwd/l3fwd_fib.c | 2 ++
examples/l3fwd/meson.build | 6 ------
3 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/examples/l3fwd/l3fwd_em.c b/examples/l3fwd/l3fwd_em.c
index 6f8d94f120..10be24c61d 100644
--- a/examples/l3fwd/l3fwd_em.c
+++ b/examples/l3fwd/l3fwd_em.c
@@ -239,6 +239,14 @@ em_mask_key(void *key, xmm_t mask)
return vec_and(data, mask);
}
+#elif defined(RTE_ARCH_RISCV)
+static inline xmm_t
+em_mask_key(void *key, xmm_t mask)
+{
+ xmm_t data = vect_load_128(key);
+
+ return vect_and(data, mask);
+}
#else
#error No vector engine (SSE, NEON, ALTIVEC) available, check your toolchain
#endif
diff --git a/examples/l3fwd/l3fwd_fib.c b/examples/l3fwd/l3fwd_fib.c
index 26d0767ae2..e02e4b3f5a 100644
--- a/examples/l3fwd/l3fwd_fib.c
+++ b/examples/l3fwd/l3fwd_fib.c
@@ -18,6 +18,8 @@
#include "l3fwd_neon.h"
#elif defined RTE_ARCH_PPC_64
#include "l3fwd_altivec.h"
+#else
+#include "l3fwd_common.h"
#endif
#include "l3fwd_event.h"
#include "l3fwd_route.h"
diff --git a/examples/l3fwd/meson.build b/examples/l3fwd/meson.build
index 75fa19b7fe..0830b3eb31 100644
--- a/examples/l3fwd/meson.build
+++ b/examples/l3fwd/meson.build
@@ -6,12 +6,6 @@
# To build this example as a standalone application with an already-installed
# DPDK instance, use 'make'
-if dpdk_conf.has('RTE_ARCH_RISCV')
- build = false
- reason = 'riscv arch not supported'
- subdir_done()
-endif
-
allow_experimental_apis = true
deps += ['hash', 'lpm', 'fib', 'eventdev']
sources = files(
--
2.30.2
next prev parent reply other threads:[~2022-06-07 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 10:46 [PATCH RESEND v4 0/8] Introduce support for RISC-V architecture Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 1/8] eal: add initial " Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 2/8] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 3/8] net/memif: set memfd syscall ID on RISC-V Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 4/8] net/tap: set BPF syscall ID for RISC-V Stanislaw Kardach
2022-06-07 10:46 ` Stanislaw Kardach [this message]
2022-06-07 10:46 ` [PATCH RESEND v4 6/8] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 7/8] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 8/8] ci: add RISCV64 cross compilation job Stanislaw Kardach
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=20220607104617.153892-6-kda@semihalf.com \
--to=kda@semihalf.com \
--cc=Frank.Zhao@starfivetech.com \
--cc=dev@dpdk.org \
--cc=mw@semihalf.com \
--cc=sam.grove@sifive.com \
--cc=upstream@semihalf.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).