From: Tim Bird <tim.bird@am.sony.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Adam Kropelin <akropel1@rochester.rr.com>,
dtor_core@ameritech.net, linux-kernel@vger.kernel.org,
celinux-dev@tree.celinuxforum.org, tpoynor@mvista.com,
geert@linux-m68k.org
Subject: Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Mon, 12 Jul 2004 10:50:22 -0700 [thread overview]
Message-ID: <40F2CF5E.8040806@am.sony.com> (raw)
In-Reply-To: <20040710182527.47534358.akpm@osdl.org>
Andrew Morton wrote:
> "Adam Kropelin" <akropel1@rochester.rr.com> wrote:
>
>>>Does 250 ms worth all this pain?
My requirement is to get to user space in 500 ms from product
cold start. It would be very nice to do so in 250 ms, to give
user space init more time. This requirement is pretty
characteristic of many CE products.
>>
>> 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.
Thanks. Even if our features aren't mainstream, if we can make them
unintrusive, it's nice to get them integrated. The help offered here,
to make this as unintrusive and danger-free as possible, is really
appreciated.
As to the number of developers and systems using this, I would wager
that developers at almost every CE company will use this (with developers
in the 100s), and that it will affect (at least) 100s of thousands of
devices (possibly millions, depending on how Linux does in cell phones).
=============================
Tim Bird
Architecture Group Co-Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
E-mail: tim.bird@am.sony.com
=============================
prev parent reply other threads:[~2004-07-12 17:49 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
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 [this message]
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=40F2CF5E.8040806@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=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=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