From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avutil/executor: Allowing thread_count be zero
Date: Mon, 17 Jun 2024 16:02:46 +0800
Message-ID: <tencent_B1DF27C46A94D31E9C738B8CE61A50AAE606@qq.com> (raw)
In-Reply-To: <171860792143.28895.946678605106841565@lain.khirnov.net>
> On Jun 17, 2024, at 15:05, Anton Khirnov <anton@khirnov.net> wrote:
>
> Quoting Zhao Zhili (2024-06-17 07:19:26)
>> From: Zhao Zhili <zhilizhao@tencent.com>
>>
>> When thread_count be zero, it will be run on current thread like
>> !HAVE_THREADS.
>
> Other APIs treat zero to mean "auto".
executor don’t detect cpu cores by itself. It’s more low level than libavcodec.
Zero thread is zero thread, literally. If we use thread_count one to mean
run on current thread, how to create a single thread then?
What’s the API do you suggest? Some negative value?
>
> --
> 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".
_______________________________________________
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:[~2024-06-17 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 5:19 Zhao Zhili
2024-06-17 7:05 ` Anton Khirnov
2024-06-17 7:21 ` Paul B Mahol
2024-06-17 8:02 ` Zhao Zhili [this message]
2024-06-17 8:45 ` Hendrik Leppkes
2024-06-17 9:27 ` Zhao Zhili
2024-06-18 11:50 ` Nuo Mi
2024-06-18 12:05 ` Steven Liu
2024-06-19 8:40 ` Nuo Mi
2024-06-19 10:39 ` Steven Liu
2024-06-18 14:23 ` Zhao Zhili
2024-06-19 8:51 ` Nuo Mi
2024-06-24 4:47 Zhao Zhili
2024-06-25 12:36 ` Nuo Mi
2024-06-27 12:57 ` Nuo Mi
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=tencent_B1DF27C46A94D31E9C738B8CE61A50AAE606@qq.com \
--to=quinkblack@foxmail.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