From: sunyuechi <sunyuechi@iscas.ac.cn>
To: Stephen Hemminger <stephen@networkplumber.org>,
Qiguo Chen <chen.qiguo@zte.com.cn>
Cc: stanislaw.kardach@gmail.com, dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH v5 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions
Date: Mon, 17 Nov 2025 12:11:54 +0800 [thread overview]
Message-ID: <8cf595fe-ab7a-4c76-aeb9-2f6e676fc2c7@iscas.ac.cn> (raw)
In-Reply-To: <20251024092722.6c623afd@phoenix>
>> This patch uses RISC-V vector instructions and zicbop prefetching to
>> optimize memory copies for 129~1600 byte ranges.
>>
>> Signed-off-by: Qiguo Chen <chen.qiguo@zte.com.cn>
>> ---
> Is there any possibility of build environment being newer than
> the run time? The Intel builds already have to deal with that problem.
Yes, it's best to use hwprobe for runtime detection, but the hwprobe
detection for the zicbop extension hasn't been merged into the kernel yet.
I'd like to refer to how other projects handle RISC-V integration;
disabling it by default at compile time should also be acceptable.
next prev parent reply other threads:[~2025-11-17 4:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 9:09 [PATCH v1 0/2] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-16 9:09 ` [PATCH v1 1/2] riscv support rte_memcpy in vector Qiguo Chen
2025-10-17 5:29 ` sunyuechi
2025-10-17 10:10 ` chen.qiguo
2025-10-17 9:36 ` [PATCH v2 0/1] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-17 9:36 ` [PATCH v2 1/1] riscv support rte_memcpy in vector Qiguo Chen
2025-10-20 9:43 ` sunyuechi
2025-10-20 12:08 ` [PATCH v3 0/1] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-20 12:08 ` [PATCH v3 1/1] lib/eal/riscv: optimize rte_memcpy with RISCV vector and zicbop extensions Qiguo Chen
2025-10-21 6:56 ` [PATCH v4 0/1] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-21 6:56 ` [PATCH v4 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions Qiguo Chen
2025-10-24 2:56 ` retest Qiguo Chen
2025-10-30 15:35 ` retest Stephen Hemminger
2025-10-24 3:04 ` retest Qiguo Chen
2025-10-24 3:12 ` retest Qiguo Chen
2025-10-24 5:04 ` retest Qiguo Chen
2025-10-24 5:41 ` [PATCH v5 0/1] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-24 5:41 ` [PATCH v5 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions Qiguo Chen
2025-10-24 7:27 ` [PATCH v6 0/1] Optimization Summary for RISC-V rte_memcpy Qiguo Chen
2025-10-24 7:27 ` [PATCH v6 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions Qiguo Chen
2025-11-17 4:19 ` sunyuechi
2025-11-17 9:12 ` chen.qiguo
2025-10-24 16:27 ` [PATCH v5 " Stephen Hemminger
2025-11-17 4:11 ` sunyuechi [this message]
2025-10-16 9:09 ` [PATCH v1 2/2] benchmark report for rte_memcpy Qiguo Chen
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=8cf595fe-ab7a-4c76-aeb9-2f6e676fc2c7@iscas.ac.cn \
--to=sunyuechi@iscas.ac.cn \
--cc=bruce.richardson@intel.com \
--cc=chen.qiguo@zte.com.cn \
--cc=dev@dpdk.org \
--cc=stanislaw.kardach@gmail.com \
--cc=stephen@networkplumber.org \
/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).