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 5/5] lavc/vp8dsp: factor R-V V EPEL functions for all lengths
Date: Sat, 25 May 2024 21:29:14 +0300
Message-ID: <24179638.ouqheUzb2q@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+vckRxKu79v7o8VnZkSHX_Frm671z2cGod718HJAybKpA@mail.gmail.com>

Le lauantaina 25. toukokuuta 2024, 21.16.22 EEST flow gg a écrit :
> Would it be better to replace the two vsetvlstatic8 and vsetvlstatic16 with
> two vsetvl?

The other option is to hard-code the most pessimistic multiplier. That would 
be easier to read and save two instructions in the head, it would most likely 
end up slower overall, due to increased latency from the vector unit in the 
main loop.

On the other hand, with vsetvl, we have the option to adjust the multiplier at 
run-time depending on hardware vector size. That will not be possible with 
vsetvli unless we patch the code live (yikes).

> This would require the previous patch and this one to work
> together,

Yes, patch order matters.

> increasing the number of lines of code

This is reducing code size by over 2 kib of code, or several hundreds of 
instructions.

> Additionally, I have a question about patch 4 'save one R-V GPR' and patch
> 5. Should they be submitted as a single patch? Because patch 4 looks
> similar to what I initially submitted, and you suggested changing it to
> save lines of code. If it is only for patch 5, shouldn't they be combined
> together?

I think people here like to have as small and many patches as possible, as is 
generally considered the right way to use Git. Since patch 4 is a very minor 
but still independent (from patch 5) improvement, it should be separate, as 
far as I understand FFmpeg's practices.

-- 
レミ・デニ-クールモン
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-05-25 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25 15:38 [FFmpeg-devel] [PATCH 1/5] lavc/vp8dsp: avoid one multiplication on RISC-V Rémi Denis-Courmont
2024-05-25 15:38 ` [FFmpeg-devel] [PATCH 2/5] lavc/vp8dsp: expand single use R-V macros Rémi Denis-Courmont
2024-05-25 15:38 ` [FFmpeg-devel] [PATCH 3/5] lavc/vp8dsp: factor R-V V bilin functions Rémi Denis-Courmont
2024-05-25 15:38 ` [FFmpeg-devel] [PATCH 4/5] lavc/vp8dsp: save one R-V GPR Rémi Denis-Courmont
2024-05-25 15:38 ` [FFmpeg-devel] [PATCH 5/5] lavc/vp8dsp: factor R-V V EPEL functions for all lengths Rémi Denis-Courmont
2024-05-25 18:16   ` flow gg
2024-05-25 18:29     ` Rémi Denis-Courmont [this message]
2024-05-25 18:56       ` flow gg
2024-05-25 19: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=24179638.ouqheUzb2q@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