From: Daniel Gregory <daniel.gregory@bytedance.com>
To: Stanislaw Kardach <stanislaw.kardach@gmail.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
dev@dpdk.org, Liang Ma <liangma@liangbit.com>,
Punit Agrawal <punit.agrawal@bytedance.com>,
Daniel Gregory <daniel.gregory@bytedance.com>
Subject: [PATCH 2/2] eal/riscv: add support for zicbop extension
Date: Thu, 30 May 2024 18:19:48 +0100 [thread overview]
Message-ID: <20240530171948.19763-3-daniel.gregory@bytedance.com> (raw)
In-Reply-To: <20240530171948.19763-1-daniel.gregory@bytedance.com>
The zicbop extension adds instructions for prefetching data into cache.
Use them to implement RISCV-specific versions of the rte_prefetch* and
rte_prefetch*_write functions.
- prefetch.r indicates to hardware that the cache block will be accessed
by a data read soon
- prefetch.w indicates to hardware that the cache block will be accessed
by a data write soon
These instructions are emitted by __builtin_prefetch on modern versions
of Clang (17.0.1+) and GCC (13.1.0+). For earlier versions, we may not
have support for assembling Zicbop instructions, so emit the word
that encodes a 'prefetch.[rw] 0(a0)' instruction.
This new functionality is controlled by a Meson flag that is disabled by
default. Whilst it's a hint, like rte_pause(), and so has no effect if
the target doesn't support the extension, it requires the address
prefetched to be loaded into a0, which may be costly.
Signed-off-by: Daniel Gregory <daniel.gregory@bytedance.com>
Suggested-by: Punit Agrawal <punit.agrawal@bytedance.com>
---
config/riscv/meson.build | 6 +++
lib/eal/riscv/include/rte_prefetch.h | 57 ++++++++++++++++++++++++++--
2 files changed, 59 insertions(+), 4 deletions(-)
diff --git a/config/riscv/meson.build b/config/riscv/meson.build
index 07d7d9da23..ecf9da1c39 100644
--- a/config/riscv/meson.build
+++ b/config/riscv/meson.build
@@ -26,6 +26,12 @@ flags_common = [
# read from /proc/device-tree/cpus/timebase-frequency. This property is
# guaranteed on Linux, as riscv time_init() requires it.
['RTE_RISCV_TIME_FREQ', 0],
+
+ # When true override the default implementation of the prefetching functions
+ # (rte_prefetch*) with a version that explicitly uses the Zicbop extension.
+ # Do not enable when using modern versions of GCC (13.1.0+) or Clang
+ # (17.0.1+). They will emit these instructions in the default implementation
+ ['RTE_RISCV_ZICBOP', false],
]
## SoC-specific options.
diff --git a/lib/eal/riscv/include/rte_prefetch.h b/lib/eal/riscv/include/rte_prefetch.h
index 748cf1b626..82cad526b3 100644
--- a/lib/eal/riscv/include/rte_prefetch.h
+++ b/lib/eal/riscv/include/rte_prefetch.h
@@ -14,21 +14,42 @@ extern "C" {
#include <rte_compat.h>
#include <rte_common.h>
+
+#ifdef RTE_RISCV_ZICBOP
+#define RTE_PREFETCH_WRITE_ARCH_DEFINED
+#endif
+
#include "generic/rte_prefetch.h"
+/*
+ * Modern versions of GCC & Clang will emit prefetch instructions for
+ * __builtin_prefetch when the Zicbop extension is present.
+ * The RTE_RISCV_ZICBOP option controls whether we emit them manually for older
+ * compilers that may not have the support to assemble them.
+ */
static inline void rte_prefetch0(const volatile void *p)
{
- RTE_SET_USED(p);
+#ifndef RTE_RISCV_ZICBOP
+ /* by default __builtin_prefetch prepares for a read */
+ __builtin_prefetch((const void *)p);
+#else
+ /* prefetch.r 0(a0) */
+ register const volatile void *a0 asm("a0") = p;
+ asm volatile (".int 0x00156013" : : "r" (a0));
+#endif
}
+/*
+ * The RISC-V Zicbop extension doesn't have instructions to prefetch to only a
+ * subset of cache levels, so fallback to rte_prefetch0
+ */
static inline void rte_prefetch1(const volatile void *p)
{
- RTE_SET_USED(p);
+ rte_prefetch0(p);
}
-
static inline void rte_prefetch2(const volatile void *p)
{
- RTE_SET_USED(p);
+ rte_prefetch0(p);
}
static inline void rte_prefetch_non_temporal(const volatile void *p)
@@ -44,6 +65,34 @@ rte_cldemote(const volatile void *p)
RTE_SET_USED(p);
}
+#ifdef RTE_RISCV_ZICBOP
+__rte_experimental
+static inline void
+rte_prefetch0_write(const void *p)
+{
+ /* prefetch.w 0(a0) */
+ register const void *a0 asm("a0") = p;
+ asm volatile (".int 0x00356013" : : "r" (a0));
+}
+
+/*
+ * The RISC-V Zicbop extension doesn't have instructions to prefetch to only a
+ * subset of cache levels, so fallback to rte_prefetch0_write
+ */
+__rte_experimental
+static inline void
+rte_prefetch1_write(const void *p)
+{
+ rte_prefetch0_write(p);
+}
+__rte_experimental
+static inline void
+rte_prefetch2_write(const void *p)
+{
+ rte_prefetch0_write(p);
+}
+#endif /* RTE_RISCV_ZICBOP */
+
#ifdef __cplusplus
}
#endif
--
2.39.2
next prev parent reply other threads:[~2024-05-30 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 17:19 [PATCH 0/2] eal/riscv: implement prefetch using zicbop Daniel Gregory
2024-05-30 17:19 ` [PATCH 1/2] eal: add flag to hide generic prefetch_write Daniel Gregory
2024-05-30 17:19 ` Daniel Gregory [this message]
2024-05-31 8:49 ` [PATCH 2/2] eal/riscv: add support for zicbop extension Daniel Gregory
2024-10-05 1:31 ` Stephen Hemminger
2024-10-07 7:48 ` Stanisław Kardach
2024-07-12 17:22 ` [PATCH 0/2] eal/riscv: implement prefetch using zicbop David Marchand
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=20240530171948.19763-3-daniel.gregory@bytedance.com \
--to=daniel.gregory@bytedance.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=liangma@liangbit.com \
--cc=punit.agrawal@bytedance.com \
--cc=roretzla@linux.microsoft.com \
--cc=stanislaw.kardach@gmail.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).