From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: 回复:Re: [Question]Inquiry Regarding RISC-V RVV Optimization for HEVC Decoding in FFmpeg
Date: Sat, 15 Nov 2025 13:51:46 +0200
Message-ID: <2279468.XDiXgnT2Zn@basile.remlab.net> (raw)
In-Reply-To: <3f548521-c75c-4ed3-a566-e21e2216288e.yunfei_zhou@linux.alibaba.com>
Nihao,
Le lauantaina 15. marraskuuta 2025, 4.50.11 Itä-Euroopan normaaliaika
yunfei_zhou--- via ffmpeg-devel a écrit :
> Segmented load/store performance: We’ve encountered similar bottlenecks in
> our video decoding optimizations. To address this, we’re actively proposing
> new vector instructions tailored for media workloads to the RISC-V
> International standards body. At the same time, we’re working closely with
> RISC-V CPU microarchitecture teams to improve the hardware efficiency of
> these memory operations.
Nathan Edge (Google / RISE) gathered a list of useful instructions for
multimedia at last year's VDD in Seoul. I do not know what came out of it
though. However as far as segmented loads and stores are concerned, I don't
think that the instruction set has a much of a problem. This looks like an
implementation limitation.
Of course, FFmpeg could use an in-register transpose instruction. There are
cases of transposition not immediately following a load or preceding a store -
particularly with video codec two-dimensional transforms. But at the same
time, FFmpeg probably has to retain support for RVV 1.0 and RVA23 processors
for a long time. Any new instruction set extension will require additional
specialised optimisations, adding to the maintenance burden. So from the open-
source project's standpoint, that really should be the last resort.
For comparison, FFmpeg is still in the process of removing MMX in favour of
SSE2 and co... Maybe we will be done before MMX turns 30.
--
德尼-库尔蒙‧雷米
https://www.remlab.net/
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-11-15 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 1:52 [FFmpeg-devel] " yunfei_zhou--- via ffmpeg-devel
2025-11-14 4:20 ` [FFmpeg-devel] " Zhao Zhili via ffmpeg-devel
2025-11-14 14:21 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-15 2:50 ` [FFmpeg-devel] 回复:Re: " yunfei_zhou--- via ffmpeg-devel
2025-11-15 11:51 ` Rémi Denis-Courmont via ffmpeg-devel [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=2279468.XDiXgnT2Zn@basile.remlab.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=remi@remlab.net \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git