Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Boot-up Time Reduction Howto

From eLinux.org
Revision as of 20:16, 24 November 2008 by FransMeulenbroeks (Talk | contribs)

Jump to: navigation, search

The items on this page constitute a list of existing techniques for reducing bootup times for embedded systems. Some of these items may also be applicable to desktop or enterprise systems, but that is not the focus.

For each individual item below, a separate page should exist. If it doesn't already exist, a new page should be created using the !HowtoTemplate. Links listed in red below are pages that are not created yet. To sign up for a task related to this HOWTO, please see the Bootup Time Howto Task List.

Introduction

Bootup Phases

This document divides the bootup process into 3 main phases:

  • Firmware initialization phase
  • Kernel initialization phase
  • User Space initialization phase

User Space usually consists of a few distinct phases also:

  • Initialization scripts (RC scripts, for desktop systems)
    • This is where most daemons and services are loaded.
  • Graphics system initialization
  • Graphical environment start
  • Application initialization

Main Technique Types

Techniques presented here can be organized according to the way they try to achieve their effect. The technique can consist of:

  1. speeding up the activity
  2. doing the activity in parallel with other initialization tasks
  3. doingthe activity later (possibly after booting is completed)
  4. avoiding doing the activity at all.

In summary, each technique describes how to take an existing bootup activity and do one of:

  • Do it faster
  • Do it in parallel
  • Do it later
  • Don't do it at all

Some techniques will consist of multiple methods (such as both speeding up and doing it in parallel).

Bootup Time Reduction Technique Outline

Following is an outline of different bootup time reduction techniques, organized by the boot phase where they are applied.

Firmware Phase

Here ase some techniques for speeding up the Firmware phase of the boot sequence:

  • [Kernel XIP] - Kernel Execute-In-Place
  • SkipFirmware - Disable firmware features to eliminate diagnostics, memory counts, etc.
  • [Parallel HD SpinUp] - Parallelize Hard Disk spinup with Kernel load
  • [Dma Copy Of Kernel On Startup] - Use DMA to copy kernel from flash to RAM

Kernel Phase

The following are techniques used to speed up the initialization of the kernel:

User Space Phase

The following are techniques for reducing the bootup time for user-space programs:

(This is a special case of eliminating unneeded RC scripts)

General Reduction Techniques

Some reduction techniques don't apply to a specific boot phase, but are general methods to reduce bootup time. These are listed here.

  • Smaller Programs - Use smaller kernel and programs for faster load times
  • Faster Memory - Use faster system memory to increase load and initialization performance

Table of Reduction Techniques

The following table summarizes the various techniques listed in this document.

Acronyms and Terms
Technique Boot Phase Description Observed reduction Notes
Kernel XIP Firmware Kernel Execute-In-Place - avoids kernel copy and decompression time 250 ms causes runtime performance loss
Skip Firmware Firmware Skip firmware probing features, like memory check, bus probing, and device detection, etc. ?? Linux re-probes busses and devices anyway, so this is usually waste of time
Parallel HD SpinUp Firwmare Start hard drive spin up before loading kernel ?? Not possible if the kernel is loaded from hard drive.
DMA Copy Of Kernel On Startup Firmware Use DMA to copy kernel from flash to RAM 180 ms .
Preset LPJ Kernel Use a hardcoded loops_per_jiffy value to avoid cost of calibration. 250 ms .
No Probe Missing Devices Kernel Avoid probing for non-existent keyboards and other devices ?? .
Small Kernel Config Kernel Reduce kernel size and length of code paths, thereby reducing execution overhead ?? .
Disable Console Kernel Turn off output to serial console during boot 250 ms .
Preconfigure PCI Kernel Preconfigure PCI bus slots on kernel command line ?? Is this even possible?
Load Drivers Later Drivers Move drivers to modules and load them later in boot sequence.) ?? Only works for drivers that can be loaded as modules late in the boot cycle.
IDE No Probe Drivers Use "noprobe" on kernel command line for IDE driver 3 sec. Depends on hardware present
Reduce Driver Busy Waits Drivers Reduce the length of driver busy waits ?? .
Short IDE Delays Drivers Reduce length of IDE initialization delays 5 sec. May be dangerous, depends on hardware
Threaded Init Drivers Replace busywaits in drivers with yields ?? Only adds value if driver can be parallelized with some other init activity.
IDE Preempt Drivers Replace busywaits in IDE drivers with yields 250 ms (decreased non-preemptibility) Already fixed in 2.6
Reduce RC Scripts RC scripts Eliminate unneeded init scripts 3 sec. Depends on required scripts
Parallel RC Scripts RC scripts Start init scripts in parallel ?? .
Defer RC Scripts RC scripts Defer some init scripts to later in boot cycle ?? .
Optimize RC Scripts RC scripts Use busybox, smaller shell, builtins, adjusted scripts 3 sec. Depends on required scripts
Custom Init Program RC scripts Use custom initialization program (eliminating RC scripts altogether) 10 sec. requires long-term maintenance of the program
Application XIP User Space Use Execute-In-Place for applications and libraries. ?? Requires uncompressed file system. Application performance may be reduced.
Segmented File System User Space Keep read-only data separate from writable data in flash storage ?? .
Reduce Flash Writes User Space Avoid writes to flash memory ?? .
Ramdisk During Boot User Space Keep writable files in RAM, and write them to flash after boot ?? .
Smaller Programs User Space Use smallest programs and configurations possible ?? Reduces program load time. It may increase cache hits.
Faster Memory General Use faster memory ?? .

Potential Techniques

Here is a list of potential techniques that have not been tried yet, to our knowledge:

  • Use different, faster, firmware
  • Cache results of find and grep during RC scripts
  • Partial XIP (this is a current project of the WG)