From: Adam Kropelin <akropel1@rochester.rr.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Fri, 9 Jul 2004 18:24:56 -0400 [thread overview]
Message-ID: <20040709182456.A20309@mail.kroptech.com> (raw)
In-Reply-To: <40EEF10F.1030404@am.sony.com>; from tim.bird@am.sony.com on Fri, Jul 09, 2004 at 12:25:03PM -0700
On Fri, Jul 09, 2004 at 12:25:03PM -0700, Tim Bird wrote:
> Finally, this code adds a new FASTBOOT menu to the kernel
> config system, where we (CE Linux Forum developers) would like
> to add this and other config options which can be used to
> reduce kernel bootup time.
<snip>
> +menuconfig FASTBOOT
> + bool "Fast boot options"
> + help
> + Say Y here to enable faster booting of the Linux kernel. If you
> + say Y here, you may be asked to provide hardcoded values for some
> + parameters that the kernel usually determines automatically.
If FASTBOOT is intended to be merely a container for individual related
options, this help text seems misleading. FASTBOOT=y alone will have no
effect on the kernel. It's just a gateway to other more specific
options. Something like this may be better:
Say Y here to select among various options that can decrease
kernel boot time. These options commonly involve providing
hardcoded values for some parameters that the kernel usually
determines automatically.
This option is useful primarily on embedded systems.
If unsure, say N.
> +config PRESET_LPJ
> + int "Preset loops_per_jiffy" if USE_PRESET_LPJ
> + help
> + This is the number of loops used by delay() to achieve a single
> + jiffy of delay inside the kernel. It is roughly BogoMips * 5000.
> + To determine the correct value for your kernel, first turn off
> + the fast booting option, compile and boot the kernel on your
> + target hardware, then see what value is printed during the
> + kernel boot. Use that value here.
Perhaps mention the new lpj= parameter is an alternative:
loops_per_jiffy can also be set via the "lpj=" kernel command
line parameter.
--Adam
next prev parent reply other threads:[~2004-07-09 21:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 19:25 [PATCH] preset loops_per_jiffy for faster booting Tim Bird
2004-07-09 22:24 ` Adam Kropelin [this message]
2004-07-09 23:35 ` Adam Kropelin
2004-07-10 0:20 ` Tim Bird
2004-07-10 2:01 ` Adam Kropelin
2004-07-10 2:01 ` Todd Poynor
2004-07-10 15:42 ` Adam Kropelin
2004-07-10 14:41 ` [Celinux-dev] " Geert Uytterhoeven
2004-07-10 15:22 ` Adam Kropelin
2004-07-10 15:54 ` Adam Kropelin
2004-07-10 18:28 ` Adam Kropelin
2004-07-10 18:19 ` Dmitry Torokhov
2004-07-10 20:14 ` Adam Kropelin
2004-07-11 1:25 ` Andrew Morton
2004-07-11 3:44 ` Adam Kropelin
2004-07-11 4:38 ` Andrew Morton
2004-07-12 17:31 ` Tim Bird
2004-07-11 4:51 ` Dmitry Torokhov
2004-07-11 4:58 ` Karim Yaghmour
2004-07-11 5:19 ` Dmitry Torokhov
2004-07-11 5:27 ` Andrew Morton
2004-07-11 7:46 ` Geert Uytterhoeven
2004-07-11 7:51 ` Andrew Morton
2004-07-11 13:41 ` Adam Kropelin
2004-07-12 18:52 ` Tim Bird
2004-07-12 19:32 ` Adam Kropelin
2004-07-12 22:41 ` Tim Bird
2004-07-13 19:24 ` Bartlomiej Zolnierkiewicz
2004-07-12 17:50 ` Tim Bird
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=20040709182456.A20309@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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