From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/7] lavc/me_cmp: R-V V pix_abs
Date: Sat, 10 Feb 2024 11:14:11 +0200
Message-ID: <6013849.lOV4Wx5bFT@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+ssHMdrNKHtQK_ZijiJ2=fdXGBdKQDMyiRCoyynKcq4iA@mail.gmail.com>
Le perjantaina 9. helmikuuta 2024, 17.34.40 EET flow gg a écrit :
> The issue here is that any load greater than e8 will fail the test(Bus
> error), so it cannot use vlse64 or similar methods...
AFAICT, data is aligned on 16 bytes here, so using larger element sizes should
not be a problem. That being the case, you can load pretty much any power-of-
two byte quantity per row up to 512 bits, as 8 segments of 64-bit elements.
That is more than enough to deal with 16-byte rows.
Of course, that results in a tiled data layout, so it only works if individual
elements are all treated equally with no cross-row calculations. This might
require trickery or not work at all for those functions that subtract adjacent
values. But your patchset seems to leave those out anyway.
--
Rémi Denis-Courmont
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".
next prev parent reply other threads:[~2024-02-10 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 15:55 flow gg
2024-02-06 16:58 ` Rémi Denis-Courmont
2024-02-07 0:01 ` flow gg
2024-02-08 19:41 ` Rémi Denis-Courmont
2024-02-08 22:39 ` flow gg
2024-02-09 10:32 ` Rémi Denis-Courmont
2024-02-09 15:34 ` flow gg
2024-02-10 9:14 ` Rémi Denis-Courmont [this message]
2024-02-10 9:15 ` Rémi Denis-Courmont
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=6013849.lOV4Wx5bFT@basile.remlab.net \
--to=remi@remlab.net \
--cc=ffmpeg-devel@ffmpeg.org \
/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