From: lucas.magasweran@ieee.org (Lucas Rangit Magasweran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bootloader sequence with time prefix (Kernelnewbies Digest, Vol 30, Issue 24)
Date: Fri, 24 May 2013 07:16:23 -0700 [thread overview]
Message-ID: <519F7637.6090303@ieee.org> (raw)
In-Reply-To: <36844.1369060821@turing-police.cc.vt.edu>
On 05/20/2013 07:40 AM, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 20 May 2013 15:07:33 +0530, Dhyan said:
>> I was working on to measure boottime for bootime optimization.
> The bootloader is probably not where you're going to find places to
> optimize.
> It's got two jobs to do - load the kernel and load the initrd. And
> it's usually
> pretty optimized to do that. About all you can do there is minimize
> the size of
> the kernel and initrd so there's less to load (and move to SSD if
> you're really
> hardcore).
>
> The only other place to really win in the boot loader is to set the
> "hit any
> key to go to the boot menu" timeout to 0 or 1 seconds. Of course,
> this means
> you have little (or zero) chance to enter an alternate kernel or
> commandline.
Valdis is absolutely right.
In case the boot loader is not so optimized or you are trying to reduce
the boot time by milliseconds try using a GPIO pin and a USB logic
analyzer (e.g. Salea Logic). Toggle a pin at key places in the boot
sequence to measure time. Setting up a timer and printing relative time
over a serial port will negatively impact your boot time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130524/88394228/attachment-0001.html
prev parent reply other threads:[~2013-05-24 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 7:07 Bootloader sequence with time prefix Dhyan
2013-05-20 7:49 ` Valdis.Kletnieks at vt.edu
2013-05-20 8:25 ` Dhyan
2013-05-20 9:10 ` Valdis.Kletnieks at vt.edu
2013-05-20 9:37 ` Dhyan
2013-05-20 14:40 ` Valdis.Kletnieks at vt.edu
2013-05-24 14:16 ` Lucas Rangit Magasweran [this message]
[not found] <mailman.28.1369300221.2741.kernelnewbies@kernelnewbies.org>
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=519F7637.6090303@ieee.org \
--to=lucas.magasweran@ieee.org \
--cc=kernelnewbies@lists.kernelnewbies.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).