From: "Martin Storsjö" <martin@martin.st> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH] cpu: Limit the number of auto threads in 32 bit builds Date: Mon, 5 Sep 2022 12:30:27 +0300 Message-ID: <20220905093027.4090687-1-martin@martin.st> (raw) Limit the returned value from av_cpu_count to sensible amounts in 32 bit builds. This chosen limit, 64, is somewhat arbitrary - a 32 bit process is capable of creating much more than 64 threads. But in many cases, multiple parts of the encoding pipeline (decoder, filters, encoders) all create a pool of threads, auto sized according to the number of cores. In one failing test, the process had managed to create 506 threads before a pthread_create call failed. In the current set of fate tests, the filter-lavd-scalenorm test seems to be the limiting factor; in a 32 bit build (arm linux, running on an aarch64 kernel), it starts failing with an auto thread count somewhere around 85. Therefore, pick the maximum with some margin below this. This fixes running fate without any manually set number of threads in 32 bit builds on machines with huge numbers of cores. --- libavutil/cpu.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/libavutil/cpu.c b/libavutil/cpu.c index 0035e927a5..094bd71d3d 100644 --- a/libavutil/cpu.c +++ b/libavutil/cpu.c @@ -233,6 +233,12 @@ int av_cpu_count(void) nb_cpus = sysinfo.dwNumberOfProcessors; #endif +#if SIZE_MAX <= UINT32_MAX + // Avoid running out of memory/address space in 32 bit builds, by + // limiting the number of auto threads. + nb_cpus = FFMIN(nb_cpus, 64); +#endif + if (!atomic_exchange_explicit(&printed, 1, memory_order_relaxed)) av_log(NULL, AV_LOG_DEBUG, "detected %d logical cores\n", nb_cpus); -- 2.25.1 _______________________________________________ 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 reply other threads:[~2022-09-05 9:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 9:30 Martin Storsjö [this message] 2022-09-05 11:45 ` Andreas Rheinhardt 2022-09-05 11:50 ` Martin Storsjö 2022-09-05 11:54 ` Andreas Rheinhardt
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=20220905093027.4090687-1-martin@martin.st \ --to=martin@martin.st \ --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