From: Henrik Gramner <henrik@gramner.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/4] lavc/pthread_frame: set worker thread names
Date: Tue, 18 Oct 2022 22:59:21 +0200
Message-ID: <CAFGUN0pSD+uHH9x-zYXC3JC+giyNwVCy-8v_JAhmh7MG8-TjdA@mail.gmail.com> (raw)
In-Reply-To: <20221018165307.28242-2-anton@khirnov.net>
On Tue, Oct 18, 2022 at 6:54 PM Anton Khirnov <anton@khirnov.net> wrote:
> +static void thread_set_name(PerThreadContext *p)
> +{
> + AVCodecContext *avctx = p->avctx;
> + int idx = p - p->parent->threads;
> + char name[16];
> +
> + snprintf(name, sizeof(name), "d:%.7s:ft%d", avctx->codec->name, idx);
> +
> + ff_thread_setname(name);
> +}
How about having some kind of prefix to indicate that those are
libavcodec threads?
Could be helpful in a scenario where a process has threads spawned by
35 different libraries.
_______________________________________________
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:[~2022-10-18 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 16:53 [FFmpeg-devel] [PATCH 1/4] lavu/thread: add an internal function for setting thread name Anton Khirnov
2022-10-18 16:53 ` [FFmpeg-devel] [PATCH 2/4] lavc/pthread_frame: set worker thread names Anton Khirnov
2022-10-18 20:59 ` Henrik Gramner [this message]
2022-10-19 4:51 ` Rémi Denis-Courmont
2022-10-19 9:06 ` [FFmpeg-devel] [PATCH] " Anton Khirnov
2022-10-18 16:53 ` [FFmpeg-devel] [PATCH 3/4] lavf: set internal " Anton Khirnov
2022-10-18 16:53 ` [FFmpeg-devel] [PATCH 4/4] fftools/ffmpeg: set " Anton Khirnov
2022-10-21 8:15 ` [FFmpeg-devel] [PATCH 1/4] lavu/thread: add an internal function for setting thread name Anton Khirnov
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=CAFGUN0pSD+uHH9x-zYXC3JC+giyNwVCy-8v_JAhmh7MG8-TjdA@mail.gmail.com \
--to=henrik@gramner.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