From: "Rémi Denis-Courmont" <remi@remlab.net>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: Michael Platzer <michael.platzer@axelera.ai>
Subject: Re: [FFmpeg-devel] RISC-V vector DSP functions: Motivation for commit 446b009
Date: Sat, 06 Jul 2024 15:05:47 +0300
Message-ID: <2952006.e9J7NaK4W3@basile.remlab.net> (raw)
In-Reply-To: <2165884.x4K2pz0Oi7@basile.remlab.net>
(Updating an old thread)
Le perjantaina 19. tammikuuta 2024, 19.14.02 EEST Rémi Denis-Courmont a écrit
:
> Hi,
>
> Le perjantaina 19. tammikuuta 2024, 17.30.00 EET Michael Platzer via ffmpeg-
> devel a écrit :
> > Commit 446b0090cbb66ee614dcf6ca79c78dc8eb7f0e37 by Remi Denis-Courmont has
> > replaced RISC-V vector loads and stores with negative stride with vrgather
> > (generalized permutation within vector registers) instructions in order to
> > reverse the elements in a vector register. The commit message explains
> > that
> > this change was done, but it does not explain why.
>
> It was faster on what the best approximation of real hardware available at
> the time, i.e. a Sipeed Lichee Pi4A board. There are no benchmarks in the
> commit because I don't like to publish benchmarks collected from
> prototypes.
FWIW, it still seems true on SpacemiT X60 (BananaPi-F3).
On that hardware, strided load/stores scale linear to the number of elements,
as you'd expect, with no optimisations for minus one stride (or more
accurately, minus element byte site). Vector gathers scale quadratic.
So for sufficiently large vectors, strided load/stores would presumably be
faster. But on real hardware with relatively small vector sizes, highest
bandwidth is achieved by unit-strided load/stores and vector gather with
LMUL=1.
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2024-07-06 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 15:30 Michael Platzer via ffmpeg-devel
2024-01-19 17:14 ` Rémi Denis-Courmont
2024-01-23 17:34 ` Michael Platzer via ffmpeg-devel
2024-01-23 18:02 ` Rémi Denis-Courmont
2024-07-06 12:05 ` Rémi Denis-Courmont [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=2952006.e9J7NaK4W3@basile.remlab.net \
--to=remi@remlab.net \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=michael.platzer@axelera.ai \
/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