public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Kropelin <akropel1@rochester.rr.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tim Bird <tim.bird@am.sony.com>,
	linux kernel <linux-kernel@vger.kernel.org>,
	CE Linux Developers List <celinux-dev@tree.celinuxforum.org>
Subject: Re: [Celinux-dev] Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Sat, 10 Jul 2004 11:22:51 -0400	[thread overview]
Message-ID: <20040710112251.A29889@mail.kroptech.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0407101639580.10242@waterleaf.sonytel.be>; from geert@linux-m68k.org on Sat, Jul 10, 2004 at 04:41:04PM +0200

On Sat, Jul 10, 2004 at 04:41:04PM +0200, Geert Uytterhoeven wrote:
> On Fri, 9 Jul 2004, Adam Kropelin wrote:
> > On Fri, Jul 09, 2004 at 05:20:07PM -0700, Tim Bird wrote:
> > > Adam Kropelin wrote:
> > +		printk("Set 'Preset loops_per_jiffy'=%lu for preset lpj.\n",
> > +			loops_per_jiffy);
> 
> > +config PRESET_LPJ
> > +	int "Preset loops_per_jiffy" if FASTBOOT
> > +	default 0
> > +	help
> > +	  This is the number of loops used by delay() to achieve a single
> > +	  jiffy of delay inside the kernel.  It is normally calculated at
> > +	  boot time, but that calculation can take up to 250 ms per CPU.
> > +	  Specifying a constant value here will eliminate that delay.
> > +
> > +	  loops_per_jiffy 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.
> 
> This is no longer true, it will always print the value if lpj=0.

True enough. I'll fix that along with the things Todd noticed.

--Adam


  reply	other threads:[~2004-07-10 14:48 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
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 [this message]
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=20040710112251.A29889@mail.kroptech.com \
    --to=akropel1@rochester.rr.com \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=geert@linux-m68k.org \
    --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