From: Arnie Chang <arnie.chang@sifive.com>
To: "Rémi Denis-Courmont" <remi@remlab.net>
Cc: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/h264chroma: RISC-V V add motion compensation for 8x8 chroma blocks
Date: Mon, 22 May 2023 22:15:35 +0800
Message-ID: <CAPUBFYHG=G9Ki-qFzp5-XBGri6dhNPjCAdzqnXRu5OpPjpk8Dw@mail.gmail.com> (raw)
In-Reply-To: <2112171.IdOJJ0czbG@basile.remlab.net>
On Sat, May 20, 2023 at 1:12 AM Rémi Denis-Courmont <remi@remlab.net> wrote:
> > + li t4, 0
> > + li t2, 0
> > + addi a5, t3, 1
> > + slli t3, a2, 2
> > +.LBB0_3: # if (xy != 0)
> > + add a4, a1, t4
> > + vsetvli zero, a5, e8, m1, ta, ma
> > + addiw t2, t2, 4
> > + vle8.v v10, (a4)
> > + add a4, a4, a2
> > + vslidedown.vi v11, v10, 1
>
> Isn't vslide1down.vx zero potentially faster than vslidedown.vi 1?
>
It depends on hardware design,
but in general, vslide1down.vi is typically not slower than vslidedown.vx
Using vslide1down.vi would be better here, I will fix it.
> > + vsetivli zero, 8, e8, m1, ta, ma
>
> Do we really need to reconfigure the active vector length so many times? I
> suspect that is not going to go down to well with some implementations.
>
We need to reconfigure it because the VL is changed.
The VL for vslidedown differs from that of the other instructions.
> + vwmaccu.vx v12, t1, v15
> > + vwmaccu.vx v16, a7, v15
> > + vsetvli zero, a5, e8, m1, ta, ma
> > + vle8.v v14, (a4)
> > + vsetivli zero, 8, e8, m1, ta, ma
> > + add a4, a0, t4
> > + add t4, t4, t3
>
> I could be totally wrong since I have no hardware to verify with, but I
> would
> assume that it is preferable to interleave independent scalar and vector
> instructions whence possible. For out-of-order processors, it shouldn't
> matter, but I suppose that it would on in-order multi-issue processors.
>
Interleaving those instructions can improve overall performance
_______________________________________________
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:[~2023-05-22 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 7:13 Arnie Chang
2023-05-17 14:54 ` Lynne
2023-05-18 8:20 ` Arnie Chang
2023-05-18 12:53 ` Ronald S. Bultje
2023-05-18 16:56 ` Lynne
2023-05-19 17:15 ` Rémi Denis-Courmont
2023-05-19 18:52 ` Lynne
2023-05-20 9:59 ` Rémi Denis-Courmont
2023-05-20 10:03 ` Rémi Denis-Courmont
2023-05-19 17:12 ` Rémi Denis-Courmont
2023-05-22 14:15 ` Arnie Chang [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='CAPUBFYHG=G9Ki-qFzp5-XBGri6dhNPjCAdzqnXRu5OpPjpk8Dw@mail.gmail.com' \
--to=arnie.chang@sifive.com \
--cc=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