Re: [FFmpeg-devel] [PATCH 1/2] avutil/executor: Allowing thread_count be zero

From: Hendrik Leppkes <h.leppkes@gmail.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 10:45:23 +0200
Message-ID: <CA+anqdyVQJPNjYe3qntkfm=1AeAvwyFv4N=11LnX38nvXRAQJQ@mail.gmail.com> (raw)
In-Reply-To: <tencent_B1DF27C46A94D31E9C738B8CE61A50AAE606@qq.com>

On Mon, Jun 17, 2024 at 10:03 AM Zhao Zhili <quinkblack@foxmail.com> wrote:
>
>
>
> > 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?

Whats the point of creating a single thread? Does the main thread ever
do something else in the meantime, or does it just wait for the job
anyway?

- Hendrik
_______________________________________________
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".