From: Stephen Hemminger <stephen@networkplumber.org>
To: dangshiwei <1138222970gg@gmail.com>
Cc: dev@dpdk.org, stanislaw.kardach@gmail.com, sunyuechi@iscas.ac.cn,
david.marchand@redhat.com
Subject: Re: [PATCH] eal/riscv: implement prefetch using __builtin_prefetch
Date: Tue, 15 Sep 2026 06:22:33 -0700 [thread overview]
Message-ID: <20260915062233.14e585dc@phoenix.local> (raw)
In-Reply-To: <20260310133524.28087-1-1138222970gg@gmail.com>
On Tue, 10 Mar 2026 21:35:24 +0800
dangshiwei <1138222970gg@gmail.com> wrote:
> RISC-V currently has no-op implementations of the rte_prefetch*
> functions. Use __builtin_prefetch() to allow the compiler to emit
> Zicbop prefetch instructions when the target supports them (GCC
> 13.1+, Clang 17.0.1+ with -march=rv*_zicbop).
>
> The Zicbop extension has no cache-level hints, so rte_prefetch1()
> and rte_prefetch2() fall back to rte_prefetch0(). The volatile
> qualifier is stripped via uintptr_t cast to satisfy
> __builtin_prefetch()'s const void * parameter without triggering
> -Wdiscarded-qualifiers.
>
> This replaces the abandoned v1 series by Daniel Gregory
> (Message-ID: 20240530171948.19763-1-daniel.gregory@bytedance.com)
> addressing reviewer feedback from Kardach and Hemminger.
>
> Signed-off-by: dangshiwei <1138222970gg@gmail.com>
> ---
There is another patch for x86 that does same thing.
https://patchwork.dpdk.org/project/dpdk/patch/20250223125215.358925-2-mattias.ronnblom@ericsson.com/
Would be good to have single common file for all arch.
prev parent reply other threads:[~2026-09-15 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 13:35 [PATCH] eal/riscv: implement prefetch using __builtin_prefetch dangshiwei
2026-03-28 11:48 ` sunyuechi
2026-03-28 16:38 ` shiwei dang
2026-05-26 3:30 ` sunyuechi
2026-09-15 13:22 ` Stephen Hemminger [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=20260915062233.14e585dc@phoenix.local \
--to=stephen@networkplumber.org \
--cc=1138222970gg@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@iscas.ac.cn \
/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.