lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f031e5-0060-4957-8cc8-9cd21e7d6304@gmail.com>
Date: Tue, 19 Aug 2025 18:09:20 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: linux-kernel@...r.kernel.org,
 Linux Doc Mailing List <linux-doc@...r.kernel.org>, corbet@....net,
 Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH 1/1] scripts/sphinx-build-wrapper: allow building PDF
 files in parallel

On Mon, 18 Aug 2025 20:10:01 +0200, Mauro Carvalho Chehab wrote:
> Use POSIX jobserver when available or -j<number> to run PDF
> builds in parallel, restoring pdf build performance. Yet,
> running it when debugging troubles is a bad idea, so, when
> calling directly via command line, except if "-j" is splicitly
> requested, it will serialize the build.
> 
> With such change, a PDF doc builds now takes around 5 minutes
> on a Ryzen 9 machine with 32 cpu threads:
> 
> 	# Explicitly paralelize both Sphinx and LaTeX pdf builds
> 	$ make cleandocs; time scripts/sphinx-build-wrapper pdfdocs -j 33
> 
> 	real	5m17.901s
> 	user	15m1.499s
> 	sys	2m31.482s
> 
> 	# Use POSIX jobserver to paralelize both sphinx-build and LaTeX
> 	$ make cleandocs; time make pdfdocs
> 
> 	real	5m22.369s
> 	user	15m9.076s
> 	sys	2m31.419s
> 
> 	# Serializes PDF build, while keeping Sphinx parallelized.
> 	# it is equivalent of passing -jauto via command line
> 	$ make cleandocs; time scripts/sphinx-build-wrapper pdfdocs
> 
> 	real	11m20.901s
> 	user	13m2.910s
> 	sys	1m44.553s
> 

Sounds promising to me!

I couldn't test this because I couldn't apply your sphinx-build-wrapper
series on top of docs-next.  :-/
Which commit does it based on?

Thanks,
Akira

> Reported-by: Akira Yokosawa <akiyks@...il.com>
> Closes: https://lore.kernel.org/linux-doc/9b3b0430-066f-486e-89cc-00e6f1f3b096@gmail.com/
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> ---
>  scripts/sphinx-build-wrapper | 141 ++++++++++++++++++++++++++---------
>  1 file changed, 106 insertions(+), 35 deletions(-)


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ