From: Chris Simmonds <chris.simmonds@2net.co.uk>
To: Andrew Murray <amurray@mpcdata.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: Embedded Linux Boot Time Poll
Date: Fri, 22 Oct 2010 16:33:48 +0100 [thread overview]
Message-ID: <4CC1AEDC.2040405@2net.co.uk> (raw)
In-Reply-To: <AANLkTi=YBzPDG6nOmQfegGOT+8nXm_6EKJE_L2uswxeu@mail.gmail.com>
On 22/10/10 00:20, Andrew Murray wrote:
> Hello,
>
> I'm performing some research [for a CELF presentation] into reducing
> boot time on embedded systems and would like to see if the embedded
> community agree with the following statement as to why Linux
> [arguably] takes so long in the first place for an unoptimised system:
>
> "Linux is general purpose, convenient and flexible. As it's general
> purpose it's likely to contain un-required functionality which results
> in more initialisation and a larger image size. As it's convenient and
> flexible it will spent time discovering devices and verifying their
> existence."
>
> Do you largely agree or disagree?
> Also do you believe that boot time isn't the highest priority when it
> comes to improving the kernel?
>
> Thanks,
>
> Andrew Murray
From my experience, your statements are broadly correct. As has been
pointed out, there are techniques to optimise the boot time in a system,
but they are not very well known to the majority of engineers working on
embedded Linux devices. The situation is not helped by the poor choices
made by many board and chip level vendors who bundle a Linux tool chain
and rootfs with their hardware. So, I believe that it is mostly a
problem of education, starting with the chip- and board- vendors.
Bye for now
Chris Simmonds
next prev parent reply other threads:[~2010-10-22 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 23:20 Embedded Linux Boot Time Poll Andrew Murray
2010-10-22 1:57 ` Nicolas Pitre
2010-10-22 14:24 ` Steven J. Magnani
2010-10-22 15:01 ` alucero
2010-10-22 15:33 ` Chris Simmonds [this message]
2010-10-24 10:17 ` Robert Schwebel
2010-10-24 16:01 ` Andrew Murray
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=4CC1AEDC.2040405@2net.co.uk \
--to=chris.simmonds@2net.co.uk \
--cc=amurray@mpcdata.com \
--cc=chris@2net.co.uk \
--cc=linux-embedded@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).