<html xmlns:v="urn:schemas-microsoft-com:vml" 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 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> <o:p> </o:p> Hello ,<o:p></o:p> I am looking into optimizing the boot / systemd service ordering for my embedded target hardware related to achieving fast boot options.<o:p></o:p> <o:p> </o:p> ---- The systemd-analyze report shown the delay between start of systemd init and the activation of my basic.target where the application services and deamons are activated is close to 4 sec. This time is being spent for the following special targets and dependent services in the following order…<o:p></o:p> <o:p> </o:p> Systemd ( activation of systemd happens @ 3.57 from cold start (uboot+kernel init))<o:p></o:p> -.mount<o:p></o:p> systemd-ask-password-wall.path<o:p></o:p> syslog.socket<o:p></o:p> remote-fs.target<o:p></o:p> systemd-shutdownd.socket<o:p></o:p> systemd-initctl.socket<o:p></o:p> -.slice<o:p></o:p> user.slice<o:p></o:p> system.slice<o:p></o:p> slices.target<o:p></o:p> system-getty.slice<o:p></o:p> system-serial\x2dgetty.slice<o:p></o:p> systemd-ask-password-console.path<o:p></o:p> paths.target<o:p></o:p> systemd-udevd-kernel.socket<o:p></o:p> systemd-udevd-control.socket<o:p></o:p> systemd-journald.socket<o:p></o:p> systemd-udev-trigger.service (1.309s)<o:p></o:p> systemd-modules-load.service (949ms)<o:p></o:p> systemd-sysctl.service (909ms)<o:p></o:p> systemd-journald.service<o:p></o:p> kmod-static-nodes.service (1.079s)<o:p></o:p> swap.target<o:p></o:p> tmp.mount (650ms)<o:p></o:p> systemd-remount-fs.service (480ms)<o:p></o:p> systemd-random-seed.service (329ms)<o:p></o:p> sys-fs-fuse-connections.mount (265ms)<o:p></o:p> systemd-tmpfiles-setup-dev.service (89ms)<o:p></o:p> systemd-udevd.service (261ms)<o:p></o:p> local-fs-pre.target<o:p></o:p> var-volatile.mount (48ms)<o:p></o:p> local-fs.target<o:p></o:p> systemd-journal-flush.service (97ms)<o:p></o:p> systemd-tmpfiles-setup.service (310ms)<o:p></o:p> systemd-update-utmp.service (189ms)<o:p></o:p> run-postinsts.service (117ms)<o:p></o:p> sys-subsystem-net-devices-eth0.device<o:p></o:p> sys-devices-platform-enet.0-net-eth0.device<o:p></o:p> dev-ttymxc0.device<o:p></o:p> sys-devices-platform-imx\x2duart.0-tty-ttymxc0.device<o:p></o:p> dev-ttymxc1.device<o:p></o:p> sys-devices-platform-imx\x2duart.1-tty-ttymxc1.device<o:p></o:p> dev-ttymxc2.device<o:p></o:p> sys-devices-platform-imx\x2duart.2-tty-ttymxc2.device<o:p></o:p> dev-ttymxc4.device<o:p></o:p> sys-devices-platform-imx\x2duart.4-tty-ttymxc4.device<o:p></o:p> dev-ttymxc3.device<o:p></o:p> sys-devices-platform-imx\x2duart.3-tty-ttymxc3.device<o:p></o:p> sys-devices-platform-soc\x2daudio.0-sound-card0.device<o:p></o:p> sound.target<o:p></o:p> sysinit.target<o:p></o:p> gpsd.socket<o:p></o:p> systemd-tmpfiles-clean.timer<o:p></o:p> timers.target<o:p></o:p> alsa-restore.service (1.263s)<o:p></o:p> dbus.socket<o:p></o:p> sockets.target<o:p></o:p> basic.target <o:p></o:p> ->>> Services listed with basic target start activation 7.5 sec)<o:p></o:p> <div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in"> <o:p> </o:p> </div> <o:p> </o:p> I looked into the documentation of systemd (boot sequence) <a href="http://man7.org/linux/man-pages/man7/bootup.7.html"> http://man7.org/linux/man-pages/man7/bootup.7.html</a><o:p></o:p> and my understanding is that the above chain of mentioned targets are per systemd recommended boot order.<o:p></o:p> <o:p> </o:p> Now based on my understanding…<o:p></o:p> <o:p> </o:p> 1/ Is there a recommended way to re-organize the boot target order ( I don’t see there is a way to fit my userlevel application executables or deamons needed for early functionality to be associated with these “primitive target” appearing in the boot chain”.<o:p></o:p> <o:p> </o:p> 2/ Is there a way to define custom target like “early-boot.target” and can be placed well on top of these special targets which can be used to start my user space applications that needs to be started well early during the boot process ( for example my full functional UI to be available within 8 sec from a cold boot which is has a X11 dependency) . So I mean that I need a way to start the X11 and my UI executable soon after systemd gets initialized and very early during the boot process.Currently the service files for the X11 and UI after associated with the basic.target and now the service activation can happen only around 7 sec after power on and when the basic.target is activated.<o:p></o:p> <o:p> </o:p> 3/ Is there any special consideration to disable these special targets like (swap.target,local-fs target if they are not used in the embedded devices?).<o:p></o:p> <o:p> </o:p> Please provide the recommendation or point to any links/previous discussions. I read through the <a href="http://freedesktop.org/wiki/Software/systemd/Optimizations/">http://freedesktop.org/wiki/Software/systemd/Optimizations/</a> a very helpful note on optimization ,but couldn’t infer much on how to work around this sequencing issue.<o:p></o:p> <o:p> </o:p> Regards<o:p></o:p> Vibin<o:p></o:p> <o:p> </o:p> <o:p></o:p> <o:p> </o:p> </div> </body> </html>