Re: [RFC v3 1/2] delay creation of initrd until end of rootfs install

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 09.04.25 13:28, 'Felix Moessbauer' via isar-users wrote:
> This patch solves major performance issues around the initramfs
> creation by ensuring that the initrd is only created once. This is
> implemented by stubbing the update-initramfs call during the package
> installing. After all apt operations are completed, we manually
> trigger the initrd creation. In case a custom initramfs is used, the
> creation is completely skipped in the image rootfs, as this would
> anyways not be used. We further unify the initrd generation in the
> rootfs and in the initramfs class.
> 
> Before that, each package install that made a initrd relevant change
> triggered the update of the initrd. As we have multiple apt calls during
> the build, this step was sometimes executed multiple times. In addition,
> the apt install step is emulated, further slowing down the initrd
> generation.
> 
> On a test build of the RPi4b target with a detached initramfs and a
> distro kernel, this patch set reduced the build time form ~50min to
> ~15min.
> 

Just to document what we discussed offline: Using a PATH-based stub
injection for update-initramfs would be much nicer, less invasive and
would avoid placing initramfs-tools into images that have no kernels.

Jan

-- 
Siemens AG, Foundational Technologies
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 visit https://groups.google.com/d/msgid/isar-users/ee30b342-577f-4972-9714-7eae7b3acbda%40siemens.com.