mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Pfiffer <andyp@osdl.org>
To: Ro0tSiEgE LKML <lkml@ro0tsiege.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Boot Speedup
Date: 05 Mar 2003 16:44:26 -0800	[thread overview]
Message-ID: <1046911465.29868.46.camel@andyp.pdx.osdl.net> (raw)
In-Reply-To: <1046909941.1028.1.camel@gandalf.ro0tsiege.org>

On Wed, 2003-03-05 at 16:19, Ro0tSiEgE LKML wrote:
> What are some things I can change/disable/etc. to cut down the boot time
> of the kernel (i386) ? I would like to get one to boot in a couple
> seconds, tops. Is this possible, and how?

To get to that kind of boot-up speed, the best way is to never shutdown.

On a StrongArm platform I worked on, we managed to put the CPU to sleep
and the DRAM controller into self-refresh mode and a few other
housekeeping chores (like checksumming our saved CPU state to be able to
verify it on resumption), and could spring back to life with the press
of a power button in about the same amount of time it took for the
cold-cathode back-light to warm up enough to see the built-in screen.

On a modern laptop, it may be possible, in theory, to accomplish the
same kind of thing.  The key is to be able to not lose the contents of
memory.  I'm not well versed on current state-of-the-art
power-management on commodity x86 platforms, so your mileage may vary.

If you want cold-start boot on a PC, you'll probably need to completely
skip the BIOS (have a look at LinuxBIOS and/or kexec), skip the probing
of devices on reboot, and drastically shorten (or run later) any
user-mode scripts that are invoked.

On the machines that I have measured (p3-800 and p4-1.7Xeon, a
well-configured kernel, after subtracting out BIOS time and stupid scsi
reprobing, is up and open for business in about 10 seconds after the
LILO handoff.  The *system* however, isn't often available for another
30 or 40 seconds, perhaps longer.

Andy



  reply	other threads:[~2003-03-06  0:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06  0:19 Ro0tSiEgE LKML
2003-03-06  0:44 ` Andy Pfiffer [this message]
2003-03-06  1:35   ` Adam Sulmicki
2003-03-06 10:01 ` Helge Hafting
2003-03-06 10:40   ` John Bradford
2003-03-26  9:23 ` Daniel Phillips
2003-03-26 14:51   ` Interpretation of termios flags on a serial driver Henrique Gobbi
2003-03-26 23:18     ` Richard B. Johnson
2003-03-26 15:33       ` Henrique Gobbi
2003-03-27  0:24         ` Russell King
2003-03-27  1:41         ` Richard B. Johnson
2003-03-27  1:01     ` Robert White

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=1046911465.29868.46.camel@andyp.pdx.osdl.net \
    --to=andyp@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@ro0tsiege.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

all inboxes | Powered by JetHome®