public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: karim@opersys.com
Cc: Adam Kropelin <akropel1@rochester.rr.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, tim.bird@am.sony.com,
	celinux-dev@tree.celinuxforum.org, tpoynor@mvista.com,
	geert@linux-m68k.org
Subject: Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Sun, 11 Jul 2004 00:19:14 -0500	[thread overview]
Message-ID: <200407110019.14558.dtor_core@ameritech.net> (raw)
In-Reply-To: <40F0C8E8.2060908@opersys.com>

On Saturday 10 July 2004 11:58 pm, Karim Yaghmour wrote:
> 
> Dmitry Torokhov wrote:
> > Do we need to encourage ordinary users to turn this option on? 99% of
> > non-embedded market is much safer with that option off...
> 
> There are other boot params that gather similar if not higher percentages.
> profile= is one of those.
>

I do not see anywhere in my boot log suggestion to activate profiling...
Nor I see recommendadtion to use idebus=66... But i will see suggesion to
set loops_per_jiffy. 

> Also, keep in mind that in a not too distant future (and indeed today for
> some folks already) recompiling and fine-tuning the Linux kernel for your
> latest gizmo will not be as foreign as your statement may make it sound.

Use of this particular option will require active tracking of kernel timer
code to ensure that lpj that was valid for kernel x.y.z is still valid for
kernel x.y.z+1. I do not beleive that normal user will ever care to do that
even in very distant future. Still, given that message in the boot log, many
will probably try the option.

I am no longer question presence of the code in the kernel, I just don't like
the message...

-- 
Dmitry

  reply	other threads:[~2004-07-11  5:19 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
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 [this message]
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=200407110019.14558.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=akropel1@rochester.rr.com \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=geert@linux-m68k.org \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.com \
    --cc=tpoynor@mvista.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