From: Thomas Monjalon <thomas@monjalon.net>
To: 孙越池 <sunyuechi@iscas.ac.cn>, uk7b@foxmail.com
Cc: dev@dpdk.org, Stanislaw Kardach <stanislaw.kardach@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3 1/4] config/riscv: detect V extension
Date: Fri, 19 Sep 2025 21:08:52 +0200 [thread overview]
Message-ID: <2941954.PIDvDuAF1L@thomas> (raw)
In-Reply-To: <39a1099c.30100.1996351c0d1.Coremail.sunyuechi@iscas.ac.cn>
19/09/2025 20:52, 孙越池:
> > Please could you add a cross file in config/riscv/ for rv64gcv
> > and use it in devtools/test-meson-builds.sh so we can test compiling
> > with the vector extension?
>
> Sure, I plan to submit this next week.
>
> > Another question about RISC-V maintenance in general,
> > 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.
You are welcome to become a maintainer of the whole arch RISC-V.
Please send a patch to add yourself.
PS: please could you find a way to have your mails formatted differently?
The quoted reply has ">" instead of ">".
Also the threading of your patches looks broken.
Don't hesitate to join on Slack if you need advices.
Thanks
next prev parent reply other threads:[~2025-09-19 19:08 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 ` 孙越池
2025-09-19 19:08 ` Thomas Monjalon [this message]
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=2941954.PIDvDuAF1L@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@iscas.ac.cn \
--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).