Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] hwcontext: Skip derivation checking for an existing device if options are set
Date: Tue, 3 May 2022 21:31:53 +0100
Message-ID: <4f6deb7a-61e1-ee16-90e4-5184b7bd8230@jkqxz.net> (raw)
In-Reply-To: <DM8P223MB03657D243AA3E7C86CBD3171BAC09@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On 03/05/2022 01:14, Soft Works wrote:
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Mark
>> Thompson
>> Sent: Tuesday, May 3, 2022 2:09 AM
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@ffmpeg.org>
>> Subject: [FFmpeg-devel] [PATCH] hwcontext: Skip derivation checking
>> for an existing device if options are set
>>
>> If options are set then the user definitely intends to create a new
>> device, so we shouldn't attempt to return an existing one.
>> ---
>>    libavutil/hwcontext.c | 26 ++++++++++++++++----------
>>    1 file changed, 16 insertions(+), 10 deletions(-)
>>
>> diff --git a/libavutil/hwcontext.c b/libavutil/hwcontext.c
>> index ab9ad3703e..c4e01e0e78 100644
>> --- a/libavutil/hwcontext.c
>> +++ b/libavutil/hwcontext.c
>> @@ -653,18 +653,24 @@ int
>> av_hwdevice_ctx_create_derived_opts(AVBufferRef **dst_ref_ptr,
>>        AVHWDeviceContext *dst_ctx, *tmp_ctx;
>>        int ret = 0;
>>
>> -    tmp_ref = src_ref;
>> -    while (tmp_ref) {
>> -        tmp_ctx = (AVHWDeviceContext*)tmp_ref->data;
>> -        if (tmp_ctx->type == type) {
>> -            dst_ref = av_buffer_ref(tmp_ref);
>> -            if (!dst_ref) {
>> -                ret = AVERROR(ENOMEM);
>> -                goto fail;
>> +    // If we were derived (possibly transitively) from a device of
>> the
>> +    // target type then we want to return that original device,
>> unless
>> +    // options are set in which case we can skip this check because
>> it
>> +    // is definitely intended to create a new device.
>> +    if (!options) {
>> +        tmp_ref = src_ref;
>> +        while (tmp_ref) {
>> +            tmp_ctx = (AVHWDeviceContext*)tmp_ref->data;
>> +            if (tmp_ctx->type == type) {
>> +                dst_ref = av_buffer_ref(tmp_ref);
>> +                if (!dst_ref) {
>> +                    ret = AVERROR(ENOMEM);
>> +                    goto fail;
>> +                }
>> +                goto done;
>>                }
>> -            goto done;
>> +            tmp_ref = tmp_ctx->internal->source_device;
>>            }
>> -        tmp_ref = tmp_ctx->internal->source_device;
>>        }
>>
>>        dst_ref = av_hwdevice_ctx_alloc(type);
>> --
> 
> This doesn't implement the matching of device parameters, which you
> were talking about:
> 
> You said that when deriving a device, an existing device should
> only be returned when the parameters are the same.
> 
> This patch is doing something quite different.

Why would that be useful in the current design?  As the documentation on create_derived states, it has two independent uses - this is the "retrieve source device" case, and for that it does not make sense to set the options argument because no new device is being created.

I will clarify the doxy on _opts.

- Mark
_______________________________________________
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:[~2022-05-03 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  0:09 Mark Thompson
2022-05-03  0:14 ` Soft Works
2022-05-03 20:31   ` Mark Thompson [this message]
2022-05-03 21:12     ` Soft Works

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=4f6deb7a-61e1-ee16-90e4-5184b7bd8230@jkqxz.net \
    --to=sw@jkqxz.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