Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Araz <primeadvice@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] [v4] avcodec/vaapi_encode: add customized surface alignment
Date: Wed, 27 Mar 2024 12:14:06 +0100
Message-ID: <CAGT-SYXp7q=LyOPb6Ew4FHaG03N+xEikMdO5y2L8fD6tCQ-g1g@mail.gmail.com> (raw)
In-Reply-To: <ac61706f-8045-4d8c-b879-dc051c203f46@jkqxz.net>

>>On Fri, Mar 22, 2024 at 11:35 AM Anton Khirnov <anton@khirnov.net> wrote:
>>Why this unnecessary complication? Just use two ints, or two uint8_t's
>>if you really need to save space, though that also seems unncessary as
>>this struct is allocated rarely and usually does not live long.

https://github.com/intel/libva/pull/794
The alignment range for log2_size of 4bit is in range of
[2**0, 2**15] = [1, 32768] this is large enough, or other way is to
directly use the alignment value, however I would want it to be in
powers of 2 and not any number, to force this condition, the common
way is to use log2_size(), which is using less bits and forcing
the alignment to be in powers of 2.

>>On Sun, Mar 24, 2024 at 5:38 PM Mark Thompson <sw@jkqxz.net> wrote:
>>What other users do you have in mind for this?  (Are you expecting
hwupload to use it as well, say?)
>>
>>If this is only used in VAAPI encode then I would suggest putting the
query there rather than adding new library API for it.
>>
>>Also agree with Anton that this form is unnecessarily confusing - just
make it a normal field, don't pack it like this.  (And possibly drop the
log2 as well?  That doesn't seem like it adds anything useful.)

The limitation is for AMD HW, and it is not limited to VAAPI, and for other
HW encoding protocols this limitation also exists.
_______________________________________________
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-03-27 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 17:02 Araz Iusubov
2024-03-22 10:35 ` Anton Khirnov
2024-03-24 16:38 ` Mark Thompson
2024-03-27 11:14   ` Araz [this message]
2024-04-01 19:34     ` Mark Thompson
2024-04-03  7:48       ` Araz

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='CAGT-SYXp7q=LyOPb6Ew4FHaG03N+xEikMdO5y2L8fD6tCQ-g1g@mail.gmail.com' \
    --to=primeadvice@gmail.com \
    --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