From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: FYI: trying to optimize initramfs generation in Debian
Date: Tue, 3 Sep 2024 07:38:50 +0000 [thread overview]
Message-ID: <f7cca223e8d6cb735af425f64408c8b772e19c1a.camel@siemens.com> (raw)
In-Reply-To: <38935123-e089-4cfc-9997-f67eaafdee17@siemens.com>
On Sat, 2024-08-24 at 09:35 +0200, 'Jan Kiszka' via isar-users wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079509
>
> We could also build a patched initramfs-tools, but I'm not yet sure
> the
> gain is worth the complication.
Hi,
thanks for bringing this up again. My other workaround to /bin/true the
generation during install and manually generate it at the end is also
still on the ISAR ML (need to re-check the state).
Anyways, it would be better to have proper support for that in Debian.
While we are at it, we could also add an option to completely disable
the initrd generation, e.g. because we will later generate a custom
one.
>
> Another, orthogonal way to optimize the generation is to provide zstd
> to
> the image so that slower gzip can be avoided by initramfs-tools (only
> recommended by initramfs-tools, not required).
Compressing the initrd with zstd has the advantage of MUCH faster
decompression at boot time. This gets relevant when e.g. adding Nvidia
GPU drivers to the initrd which are huge. For details, please also see
[1].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076582
Felix
> Still, initramfs creation
> is more than compression.
>
> Jan
>
> --
> Siemens AG, Technology
> Linux Expert Center
>
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/f7cca223e8d6cb735af425f64408c8b772e19c1a.camel%40siemens.com.
prev parent reply other threads:[~2024-09-03 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 7:35 'Jan Kiszka' via isar-users
2024-09-03 7:38 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=f7cca223e8d6cb735af425f64408c8b772e19c1a.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
/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