From: Andrew Morton <akpm@osdl.org>
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: dtor_core@ameritech.net, 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: Sat, 10 Jul 2004 18:25:27 -0700 [thread overview]
Message-ID: <20040710182527.47534358.akpm@osdl.org> (raw)
In-Reply-To: <099101c466ba$7d75aa30$03c8a8c0@kroptech.com>
"Adam Kropelin" <akropel1@rochester.rr.com> wrote:
>
> > Does 250 ms worth all this pain?
>
> On a desktop box, almost certainly not. On a massive SMP machine, maybe. On
> an embedded system that is required to boot in a ridiculously short time,
> absolutely.
Yes, it's pretty small beer, but we do recognise that although the number
of development teams which use features like this is small, the number of
systems is large, so the features are correspondingly more important.
One of the services which we kernel developers provide the downstream
kernel users is the hosting and maintenance of their code so they don't
have to carry important stuff off-stream, and when the changes are this
small and simple, I don't see a problem with merging them, even if none of
"us" will use the feature.
wrt this particular patch:
a) I don't see much point in making it configurable. Just add the boot
option and be done with it. The few hundred bytes of extra code will be
dropped from core anyway.
The main reason for this is that most people won't turn on the config
option, so your new code could get accidentally broken quite easily.
Plus it removes some ifdefs.
b) Coding style consistency, please:
Replace things like
/* Do a binary approximation to get loops_per_jiffy set to
equal one clock (up to lps_precision bits) */
with
/*
* Do a binary approximation to get loops_per_jiffy set to
* equal one clock (up to lps_precision bits)
*/
while ( lps_precision-- && (loopbit >>= 1) ) {
should be
while (lps_precision-- && (loopbit >>= 1)) {
Yes, some of the code was already like that, but let's regularise these
things as we go.
next prev parent reply other threads:[~2004-07-11 1:26 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 [this message]
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=20040710182527.47534358.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=akropel1@rochester.rr.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=dtor_core@ameritech.net \
--cc=geert@linux-m68k.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.