From: "Ihar \"Philips\" Filipau" <filia@softhome.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6 size increase
Date: Thu, 31 Jul 2003 20:02:12 +0200 [thread overview]
Message-ID: <3F2959A4.4070605@softhome.net> (raw)
In-Reply-To: <20030731172046.GH27214@ip68-0-152-218.tc.ph.cox.net>
Tom Rini wrote:
>>
>> You didn't get my point.
>> My appliances do not need sleep/shutdown at all.
>> Not every embedded system is a handheld ;-)
>
>
> That certainly is true, yes. They might want to power things down when
> the user isn't there (or maybe they don't, I don't know what you're
> making :)). And I did originally say 'some'.
>
Can you imagine teapot?
State of your system - on/off. Power saving as done by user herself:
power is consumed only when user want to boil the water ;-)
Two devices I was working on were little bit more complicated and I
had internal UPS to be able to handle power offs/fails gracefuly (like
switching off of LCD + save of the mechanics state).
As for me - I already expressed my point on subject: we should fix
compiler and language (C's inline is definitely not ehough to express
our intentions to compiler). That's the compiler should be optimized to
gain space for performace or gain performance for space.
And sure kernel should be more configurable too.
next prev parent reply other threads:[~2003-07-31 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cArb.74D.1@gated-at.bofh.it>
[not found] ` <cUTh.6JZ.33@gated-at.bofh.it>
[not found] ` <eLiy.31J.3@gated-at.bofh.it>
[not found] ` <eLBW.3eJ.7@gated-at.bofh.it>
[not found] ` <eLVb.3yF.1@gated-at.bofh.it>
[not found] ` <eOJn.5NI.1@gated-at.bofh.it>
[not found] ` <f1dJ.GS.21@gated-at.bofh.it>
[not found] ` <faTE.2LQ.3@gated-at.bofh.it>
[not found] ` <fd56.4Te.9@gated-at.bofh.it>
[not found] ` <fdRv.5uB.9@gated-at.bofh.it>
[not found] ` <fnHd.54o.19@gated-at.bofh.it>
2003-07-31 16:31 ` Kernel 2.6 size increase Ihar "Philips" Filipau
2003-07-31 16:43 ` Tom Rini
2003-07-31 17:04 ` Ihar "Philips" Filipau
2003-07-31 17:20 ` Tom Rini
2003-07-31 18:02 ` Ihar "Philips" Filipau [this message]
2003-07-28 17:13 [uClinux-dev] " Nicolas Pitre
2003-07-28 23:02 ` Bernardo Innocenti
2003-07-29 2:36 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 18:46 Bernardo Innocenti
2003-07-23 19:14 ` Richard B. Johnson
2003-07-23 20:07 ` David S. Miller
2003-07-23 21:47 ` Randy.Dunlap
2003-07-23 22:07 ` [uClinux-dev] " Bernardo Innocenti
2003-07-23 22:27 ` Willy Tarreau
2003-07-24 20:27 ` Bernardo Innocenti
2003-07-29 22:29 ` Tom Rini
2003-07-29 22:48 ` Alan Cox
2003-07-29 23:06 ` Tom Rini
2003-07-30 2:07 ` Miles Bader
2003-07-30 15:33 ` Tom Rini
2003-07-31 1:49 ` Miles Bader
2003-07-31 4:17 ` Tom Rini
2003-07-31 5:03 ` Miles Bader
2003-07-31 15:24 ` Tom Rini
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=3F2959A4.4070605@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).