DPDK patches and discussions
 help / color / mirror / Atom feed
From: 孙越池 <sunyuechi@iscas.ac.cn>
To: "Thomas Monjalon" <thomas@monjalon.net>
Cc: uk7b@foxmail.com, dev@dpdk.org,
	 "Stanislaw Kardach" <stanislaw.kardach@gmail.com>,
	 "Bruce Richardson" <bruce.richardson@intel.com>
Subject: Re: Re: [PATCH v3 1/4] config/riscv: detect V extension
Date: Sat, 20 Sep 2025 02:52:06 +0800 (GMT+08:00)	[thread overview]
Message-ID: <39a1099c.30100.1996351c0d1.Coremail.sunyuechi@iscas.ac.cn> (raw)
In-Reply-To: <3159839.72vocr9iq0@thomas>

&gt; Please could you add a cross file in config/riscv/ for rv64gcv
&gt; and use it in devtools/test-meson-builds.sh so we can test compiling
&gt; with the vector extension?

Sure, I plan to submit this next week.

&gt; Another question about RISC-V maintenance in general,
&gt; what do you think about other pending patches for RISC-V?

I would like to prioritize merging the hwprobe detection. The related work is already mostly done here:

[PATCH v3 0/9] riscv: implement accelerated crc using zbc

The next step is to contact the author for a rebase and then review it. After that, the following patch will be handled:

[PATCH 0/2] eal/riscv: implement prefetch using zicbop

In addition, our team has several riscv v extension optimization patches that we are refining and will submit soon.

I would prefer to be added as a maintainer, as this might make communication with other authors more efficient.


&gt; -----原始邮件-----
&gt; 发件人: "Thomas Monjalon" <thomas@monjalon.net>
&gt; 发送时间: 2025-09-20 02:16:22 (星期六)
&gt; 收件人: "Sun Yuechi" <sunyuechi@iscas.ac.cn>, uk7b@foxmail.com
&gt; 抄送: dev@dpdk.org, "Stanislaw Kardach" <stanislaw.kardach@gmail.com>, "Bruce Richardson" <bruce.richardson@intel.com>
&gt; 主题: Re: [PATCH v3 1/4] config/riscv: detect V extension
&gt; 
&gt; 19/09/2025 18:33, uk7b@foxmail.com:
&gt; &gt; From: Sun Yuechi <sunyuechi@iscas.ac.cn>
&gt; &gt; 
&gt; &gt; This patch is derived from "config/riscv: detect presence of Zbc
&gt; &gt; extension with modifications".
&gt; &gt; 
&gt; &gt; The RISC-V C api defines architecture extension test macros
&gt; &gt; These let us detect whether the V extension is supported on the
&gt; &gt; compiler and -march we're building with. The C api also defines V
&gt; &gt; intrinsics we can use rather than inline assembly on newer versions of
&gt; &gt; GCC (14.1.0+) and Clang (18.1.0+).
&gt; &gt; 
&gt; &gt; If the V extension and intrinsics are both present and we can detect
&gt; &gt; the V extension at runtime, we define a flag, RTE_RISCV_FEATURE_V.
&gt; &gt; 
&gt; &gt; Signed-off-by: Sun Yuechi <sunyuechi@iscas.ac.cn>
&gt; 
&gt; Series merged with style improvements, thanks.
&gt; 
&gt; Please could you add a cross file in config/riscv/ for rv64gcv
&gt; and use it in devtools/test-meson-builds.sh so we can test compiling
&gt; with the vector extension?
&gt; 
&gt; Another question about RISC-V maintenance in general,
&gt; what do you think about other pending patches for RISC-V?
&gt; 
</sunyuechi@iscas.ac.cn></sunyuechi@iscas.ac.cn></bruce.richardson@intel.com></stanislaw.kardach@gmail.com></sunyuechi@iscas.ac.cn></thomas@monjalon.net>

  reply	other threads:[~2025-09-19 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250919163358.2887335-1-uk7b@foxmail.com>
2025-09-19 16:33 ` uk7b
2025-09-19 18:16   ` Thomas Monjalon
2025-09-19 18:52     ` 孙越池 [this message]
2025-09-19 19:08       ` Thomas Monjalon
2025-09-19 16:33 ` [PATCH v3 2/4] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-09-19 16:33 ` [PATCH v3 3/4] lib/fib: R-V V rte_fib_lookup_bulk uk7b
2025-09-19 17:48   ` Thomas Monjalon
2025-09-19 17:59     ` 孙越池
2025-09-19 16:33 ` [PATCH v3 4/4] riscv: override machine_args only when default uk7b

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=39a1099c.30100.1996351c0d1.Coremail.sunyuechi@iscas.ac.cn \
    --to=sunyuechi@iscas.ac.cn \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stanislaw.kardach@gmail.com \
    --cc=thomas@monjalon.net \
    --cc=uk7b@foxmail.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).