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 v5] lavc/vvc_mc: R-V V avg w_avg
Date: Mon, 08 Jul 2024 18:41:33 +0300
Message-ID: <22345749.xTyhic22qF@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+vuPA2J0S6T+3At4JUzy4BB6DeMYr7oOuBSuLJrRdPCCg@mail.gmail.com>

Le maanantaina 1. heinäkuuta 2024, 19.09.01 EEST flow gg a écrit :
> I reviewed it again, the purpose of is_w is to limit lmul to a maximum of
> 1/4 of vlen,

1/4 of vlen? Do you mean limit to EMUL=1 for EEW=32 and EMUL=1/4 for EEW=8?

Limiting LMUL to less than 1 at maximum EEW is useless from a functional 
standpoint, since fractional registers cannot be addressed individually. (Of 
course it might still be useful for performance reasons.)

> to prevent vector register shortage, which can also be
> considered as vset limiting lmul. I renamed it to quarter_len_limit.

TBH, I don't really understand.

If a lower LMUL limit is reached, then specialisations for the corresponding 
VLEN are simply unncessary/infeasible and the code for lower VLEN should be 
used.

If a higher LMUL limit is reached due to register pressure (or the 8 hard 
limit), then the given VLEN cannot be supported at all, or requires some 
completely different code.

Either way, I don't really follow why vsetvlfixed macros need to be involved.

-- 
雷米‧德尼-库尔蒙
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-07-08 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 13:39 uk7b
2024-07-01 13:40 ` flow gg
2024-07-01 14:28   ` Rémi Denis-Courmont
2024-07-01 16:06     ` uk7b
2024-07-01 16:09       ` flow gg
2024-07-08 15:41         ` Rémi Denis-Courmont [this message]
2024-07-10 10:02           ` [FFmpeg-devel] [PATCH] " uk7b
2024-07-16 14:21             ` Rémi Denis-Courmont
2024-07-18 15:02               ` uk7b
2024-07-18 15:04               ` flow gg
2024-07-19 15:55                 ` Rémi Denis-Courmont
2024-07-21 13:43                   ` uk7b
2024-07-21 13:45                   ` flow gg
2024-07-10 10:04           ` [FFmpeg-devel] [PATCH v5] " 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=22345749.xTyhic22qF@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