From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] libavutil/hwcontect_cuda: add option to use current CUDA context
Date: Thu, 14 Sep 2023 16:03:18 +0200
Message-ID: <169470019868.20400.10524960200868191992@lain.khirnov.net> (raw)
In-Reply-To: <CAJZRZVnobJQ6wqhBn61mkAtUjsQSOwOg8EyWC_qf_6UnuMKdyA@mail.gmail.com>
Quoting Roman Arzumanyan (2023-09-14 09:26:52)
> Hello,
>
> This is the second patch of the group which adds the option to use CUDA
> context current to calling thread. It simplifies the usage of ffmpeg
> libraries in applications which rely on CUDA runtime API.
>
> Example:
>
> AVDictionary *opts = NULL;
>
> AVBufferRef *hwDeviceCtx;
>
>
> av_dict_set(&opts, "current_ctx", "1", 0);
>
> av_hwdevice_ctx_create(&hwDeviceCtx, type, NULL, opts, 0);
Use av_hwdevice_ctx_alloc() av_hwdevice_ctx_init() then.
--
Anton Khirnov
_______________________________________________
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".
next prev parent reply other threads:[~2023-09-14 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:26 Roman Arzumanyan
2023-09-14 10:00 ` Timo Rothenpieler
2023-09-14 13:29 ` Roman Arzumanyan
2023-09-14 13:32 ` Timo Rothenpieler
2023-09-14 14:03 ` Anton Khirnov [this message]
[not found] ` <CAJZRZVm1yM0n5ri-X7FZq1A+X2E1GmpsdDu6hQN5t3wpjbY6=A@mail.gmail.com>
[not found] ` <7984201b-83b4-4d51-9d5b-d70e958bf399@rothenpieler.org>
2023-09-14 16:52 ` Roman Arzumanyan
2023-09-14 16:54 ` Timo Rothenpieler
2023-09-19 8:18 ` Roman Arzumanyan
2023-09-19 12:25 ` Timo Rothenpieler
2023-09-28 17:27 ` Timo Rothenpieler
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=169470019868.20400.10524960200868191992@lain.khirnov.net \
--to=anton@khirnov.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