From: Stephen Hemminger <stephen@networkplumber.org>
To: Qiguo Chen <chen.qiguo@zte.com.cn>
Cc: sunyuechi@iscas.ac.cn, 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: Fri, 24 Oct 2025 09:27:22 -0700 [thread overview]
Message-ID: <20251024092722.6c623afd@phoenix> (raw)
In-Reply-To: <20251024054128.1569133-2-chen.qiguo@zte.com.cn>
On Fri, 24 Oct 2025 13:41:28 +0800
Qiguo Chen <chen.qiguo@zte.com.cn> wrote:
> 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.
next prev parent reply other threads:[~2025-10-24 16:27 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 ` Stephen Hemminger [this message]
2025-11-17 4:11 ` [PATCH v5 " sunyuechi
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=20251024092722.6c623afd@phoenix \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=chen.qiguo@zte.com.cn \
--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.