From: Nicolas Schier <nicolas@fjasle.eu>
To: Mirsad Todorovac <mirsad.todorovac@alu.hr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] Very long .deb package build times for bindeb-pkg build target
Date: Thu, 11 Jan 2024 16:37:28 +0100 [thread overview]
Message-ID: <ZaALOOhEdBP70lDH@bergen.fjasle.eu> (raw)
In-Reply-To: <c2adb439-0dea-4de1-996e-5a0caa5c729d@alu.unizg.hr>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi Mirsad,
On Thu 11 Jan 2024 13:22:39 GMT, Mirsad Todorovac wrote:
> Hi,
>
> With this new release, it seems that Debian kernel build uses "xz" in single-
> threaded mode:
>
> Tasks: 484 total, 2 running, 481 sleeping, 0 stopped, 1 zombie
> %Cpu(s): 2.5 us, 2.2 sy, 6.3 ni, 85.1 id, 2.3 wa, 0.0 hi, 1.7 si, 0.0 st
> MiB Mem : 64128.3 total, 524.3 free, 5832.0 used, 58540.9 buff/cache
> MiB Swap: 32760.0 total, 32758.7 free, 1.2 used. 58296.3 avail Mem
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
> COMMAND
>
> 978084 marvin 30 10 112440 97792 2432 R 100.0 0.1 29:30.23 xz
>
>
> Before dpkg-deb was using up to 3200% of CPU time on a 16 core SMT CPU.
>
> Can it be something with dpkg-deb --thread-max=%n option?
I cannot find any --thread-max option in Linux tree. Do you call
dpkg-deb manually or somehow induce a thread maximum?
> Waiting for half an hour just for the build of linux-image-...-dbg package
> seems like an overkill ...
With current v6.7 release tree I do not see the reported slow-downs
when building bindeb-pkg; I tested by cross-compiling for arm64 on
amd64 with CONFIG_MODULE_COMPRESS_XZ=y and =n).
Both take roughly 5mins on my 24-core i9 system.
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-11 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 12:22 Mirsad Todorovac
2024-01-11 15:37 ` Nicolas Schier [this message]
2024-01-11 22:48 ` Mirsad Todorovac
2024-01-13 5:40 ` Masahiro Yamada
2024-01-13 11:27 ` Mirsad Todorovac
2024-01-13 15:16 ` Masahiro Yamada
2024-01-13 21:09 ` Mirsad Todorovac
2024-01-16 11:21 ` Masahiro Yamada
2024-01-17 19:17 ` Mirsad Todorovac
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=ZaALOOhEdBP70lDH@bergen.fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.hr \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®