<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-SE" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> Thanks for the link Brian. Very valuable. <o:p></o:p> <o:p> </o:p> Have you discussed moving <a href="file:///CentOS/automotive/src/boot-time-analysis-tools/-/tree/main/cntvct-log">cntvct-log</a> to systemd-analyze? IMHO, systemd can have better control when the target is reached to record the wall time. <o:p></o:p> <o:p> </o:p> Umut <o:p></o:p> <o:p> </o:p> <div id="mail-editor-reference-message-container"> <div> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: systemd-devel <systemd-devel-bounces@lists.freedesktop.org> on behalf of Brian Masney <bmasney@redhat.com> Date: Thursday, 26 September 2024 at 03:07 To: Dharma.B@microchip.com <Dharma.B@microchip.com> Cc: serenissi@inventati.org <serenissi@inventati.org>, systemd-devel@lists.freedesktop.org <systemd-devel@lists.freedesktop.org> Subject: Re: [systemd-devel] Exploring Minimal Systemd in Initramfs for Faster Boot<o:p></o:p> </div> <div> On Wed, Sep 25, 2024 at 03:53:36PM +0000, Dharma.B@microchip.com wrote: > yes something similar to this, I will experiment this and get back to you. > > and I think since the egt service and its libraries depend on the full > rootfs, integrating initramfs might not provide significant benefits in > terms of faster launch time. The time saved by using an initramfs to > launch basic services earlier would likely be offset by the delay in > mounting the root filesystem, which is necessary for accessing the egt > libraries. There are some drawbacks to putting your early service in the initramfs and having it persist across the switch root to when systemd is started again from the root filesystem. - The initrd is a cpio archive, and increasing the size of the initrd is going to increase the kernel boot time since it will need to uncompress and extract the larger cpio archive. - Any services started from the initrd will be started before the SELinux policy is loaded. Services started from the initrd will run with the kernel_t label. - Services started from the initrd can't depend on almost anything like mounts, devices, services, dbus, etc so it's difficult to develop software of any complexity. - Adding all of these dependencies to the initrd is only going to move the timing bottlenecks booting from the root filesystem to the initrd. - Directives like Restart=always will likely not work as expected. Personally I think that you should have the initramfs be small enough to only get you to the root filesystem and start your early service from the root filesystem. Shameless self plug: Here's a presentation that I gave last month at DevConf.us in Boston with Eric Curtin and Ed Chong about some of the boot speed optimizations that a group of us worked on at Red Hat: <a href="https://pretalx.com/devconf-us-2024/talk/HXVPHC/">https://pretalx.com/devconf-us-2024/talk/HXVPHC/</a> . The talk also lists some upstream patch sets that you will want to consider including in your kernel to help with boot time. Brian<o:p></o:p> </div> </div> </div> </div> </div> </body> </html>