Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 3/3] lavc/svq1enc: R-V V ssd_int8_vs_int16
Date: Sun, 07 Jan 2024 10:03:00 +0200
Message-ID: <121759504.UfbjOsXcyo@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+vxoZpYZXYBfU37av1ko=N4sb32=duW2Zq7BnqGztDjXg@mail.gmail.com>

Le sunnuntaina 7. tammikuuta 2024, 3.33.39 EET flow gg a écrit :
> I tested it, and indeed using vwsub is faster. Updated it in the reply.
> 
> ---
> 
> I have a question: if I tweak the load order a bit, using one less vset, it
> leads to being slower (the patch I submitted is 13.2, if I make the
> following change, the time would be 15.2).
> But I thought it would be faster.

I would guess that v0 is needed before v8 in the internal implementation of 
vwsub. This kind of makes sense as the element still need to be sign-extended. 
Thus vwsub ends up stalling the pipeline in wait for vle8 to complete. That's 
just a guess though, as I don't have internal cycle timing documentation.

> - vsetvli      t0, a2, e8, m2, tu, ma
> - vle8.v       v0, (a0)
> - sub          a2, a2, t0
> - vsetvli      zero, t0, e16, m4, tu, ma
> - vle16.v      v8, (a1)
> - vsetvli      zero, t0, e8, m2, tu, ma
> - vwsub.wv     v16, v8, v0
> 
> + vsetvli      t0, a2, e16, m4, tu, ma
> + vle16.v      v8, (a1)
> + sub          a2, a2, t0
> + vsetvli      zero, t0, e8, m2, tu, ma
> + vle8.v       v0, (a0)
> + vwsub.wv     v16, v8, v0

-- 
雷米‧德尼-库尔蒙
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".

  reply	other threads:[~2024-01-07  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 11:57 flow gg
2023-12-30 12:15 ` Rémi Denis-Courmont
2023-12-30 14:00   ` flow gg
2023-12-30 14:01     ` flow gg
2023-12-30 15:45     ` Rémi Denis-Courmont
2023-12-30 16:20   ` flow gg
2024-01-04 16:00     ` Rémi Denis-Courmont
2024-01-05  0:56       ` flow gg
2024-01-06 15:04         ` Rémi Denis-Courmont
2024-01-07  1:33           ` flow gg
2024-01-07  8:03             ` Rémi Denis-Courmont [this message]
2024-01-07  8:36               ` flow gg
2024-01-16 18:00                 ` Rémi Denis-Courmont
2024-01-16 18:04             ` Rémi Denis-Courmont
2024-01-16 18:46               ` flow gg

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=121759504.UfbjOsXcyo@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