From: Andrew Murray <amurray@mpcdata.com>
To: linux-embedded@vger.kernel.org
Subject: [RFC] Kernel 'boot cache' to reduce boot time
Date: Tue, 31 Aug 2010 20:13:09 +0100 [thread overview]
Message-ID: <AANLkTimJkPD=shB9oi3ASocaLEpG=C7oDJMbq8BEy2Fe@mail.gmail.com> (raw)
Hello,
I have a suggestion for a kernel framework which aims to reduce boot
time in embedded devices and would be interested in hearing your
feedback.
A large portion of kernel boot time is spent in driver probe functions
often waiting for hardware for example calculating LPJ values or
trying to determine what type of camera is connected (PAL/NTSC) etc.
However for most embedded devices the hardware remains constant and
these probes always determine the same information. Therefore boot
time can be decreased by removing some of this probe code and
replacing it with known values.
To some extent some of these optimisations have already been done
through a variety of methods - for example the LPJ calculation can be
bypassed with the lpj= parameter and some drivers have their own
methods. My solution aims to generalise these solutions...
The solution is to provide a very simple framework which will allow
drivers to identify and record such values (LPJ, camera type, decoder
chip version) during boot. Once booted the user can obtain a
collection of these values and pass them back to the kernel on
subsequent boots. During subsequent boots - drivers upon realising
these values have already been provided can bypass some of their probe
code and thus reducing boot time. Taking advantage of this framework
would be very trivial for drivers.
I wanted to see your views on the overall solution prior to
considering how it could be implemented.
Thanks,
Andrew Murray
next reply other threads:[~2010-08-31 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:13 Andrew Murray [this message]
2010-08-31 19:52 ` [RFC] Kernel 'boot cache' to reduce boot time Tim Bird
2010-08-31 20:15 ` Andrew Murray
2010-09-01 2:40 ` Grant Likely
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='AANLkTimJkPD=shB9oi3ASocaLEpG=C7oDJMbq8BEy2Fe@mail.gmail.com' \
--to=amurray@mpcdata.com \
--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).