From: Diego Iastrubni <diegoiast@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Systemd update
Date: Mon, 16 Jul 2012 09:03:31 +0300 [thread overview]
Message-ID: <CALR4fE+nyZZXCGVOSRJM=rir4eYE4L0_Y7K+KZE5wvmUL8dFTA@mail.gmail.com> (raw)
In-Reply-To: <CADiAo4KwLhtG-ZpaBBSRQAeDBjKW9XCxAm00ZHUKw2NF97dEMg@mail.gmail.com>
(forwarding to the list, I hope you don't mind)
On Mon, Jul 16, 2012 at 5:15 AM, Dmitry Golubovsky <golubovsky@gmail.com>wrote:
>
> Here is dmesg output on a VM:
>
> http://pastebin.com/ZbQmMiTU
>
> [ 16.881460] systemd[1]: Startup finished in 14s 40ms 662us (kernel)
> + 2s 840ms 704us (userspace) = 16s 881ms 366us.
>
> of these 16sec:
>
> [ 0.392041] Trying to unpack rootfs image as initramfs...
> [ 13.790005] Freeing initrd memory: 37216k freed
>
> 13 secs were spent to unpack initrd. So it could be under 10sec from
> boot to DHCP ready.
>
>
I concern is this: *is* systemd faster then traditional int?
Does paralyzing those things decrease boot time? Can this benefit the
embedded community?
I would like to review a similar setup for something like the RPI and
measure there. I need to find time for this (I am still fighting my RPI
setup... the biggest problem is that its not trivial to get a console.. so
all I have to test is my 40" TV... not ideal for kernel messages...)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120716/301e312c/attachment.html>
next prev parent reply other threads:[~2012-07-16 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 16:08 [Buildroot] Systemd update Dmitry Golubovsky
2012-07-15 14:19 ` Diego Iastrubni
2012-07-15 17:27 ` Dmitry Golubovsky
[not found] ` <CADiAo4KwLhtG-ZpaBBSRQAeDBjKW9XCxAm00ZHUKw2NF97dEMg@mail.gmail.com>
2012-07-16 6:03 ` Diego Iastrubni [this message]
2012-07-16 9:19 ` Dmitry Golubovsky
2012-07-16 9:32 ` Alex Bradbury
2012-07-16 9:41 ` Thomas Petazzoni
2012-07-16 9:54 ` Alex Bradbury
2012-07-16 9:09 ` Maxime Ripard
2012-07-16 9:15 ` Dmitry Golubovsky
2012-07-16 9:16 ` Thomas Petazzoni
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='CALR4fE+nyZZXCGVOSRJM=rir4eYE4L0_Y7K+KZE5wvmUL8dFTA@mail.gmail.com' \
--to=diegoiast@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.