linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Kaiser <rob@sysgo.de>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux-kernel@vger.kernel.org, eccesys@topmail.de
Subject: Re: Disk is cheap?
Date: Mon, 26 Feb 2001 12:32:32 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.21.0102261204240.9294-100000@dagobert.svc.sysgo.de> (raw)
In-Reply-To: <20010224145935.D5160@bacchus.dhis.org>



On Sat, 24 Feb 2001, Ralf Baechle wrote:

> On Wed, Jan 31, 2001 at 02:29:54PM +0100, Robert Kaiser wrote:
> 
> > Perhaps a more convincing argument may be that in embedded devices,
> > disk as well as memory and CPU power are _not_ cheap.
> > 
> > The more resources Linux requires, the less are it's chances of being
> > accepted as a viable alternative in embedded systems.
> > 
> > > I'm still stuck with a P-133, 56 MB RAM (60-70 ns, some EDO,
> > > some FPM) and not only Linux but also W2K on a 2.1 and a 0.8 GB
> > > HDD.
> > 
> > That would be _a_ _lot_ for an embedded system!
> 
> Oh this common missconception that embedded system equals small systems.

I didn't say that. I'm talking about what's common in embedded systems
and it is _very_ common for an embedded system to be small both in
mechanical dimension and computational horsepower. This is not a
misconception but simply practical experience.

> There are embedded systems that outrun supercomputers without sweating,
> have gigs of RAM and sometimes if you look at them closly even have the
> names of well known big iron companies on their boards.

Sure these systems exist, but trust me, they are a very small fraction
of a very big market.

> The whole
> embedded term is just so weakly defined and everybody seem to have his
> personal definition

How about this: An embedded system is a computer system designed to
fulfill a particular purpose.

Since embedded systems are usually made in large quantities, there is a
strong pressure to make them as cheap as possible. Thus, the amount
of resources assigned to a system is usually just barely enough for
it to fulfill it's purpose. If it has gigs of RAM, you can be sure it
needs every bit of it for doing whatever it is supposed to do.

Running on low resources is symptomatic to all embedded systems.

Helau

Rob

----------------------------------------------------------------
Robert Kaiser                          email: rkaiser@sysgo.de
SYSGO RTS GmbH                         http://www.elinos.com
Am Pfaffenstein 14                     http://www.sysgo.de
D-55270 Klein-Winternheim / Germany    


  reply	other threads:[~2001-02-26 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 13:29 Disk is cheap? Robert Kaiser
2001-01-31 14:55 ` Patrizio Bruno
2001-01-31 16:12   ` Robert Kaiser
2001-02-01 12:34     ` Wojtek Pilorz
2001-02-03 12:55     ` Pavel Machek
2001-02-06 14:49       ` Robert Kaiser
2001-02-06 15:28         ` Hacksaw
2001-02-06 15:30           ` Robert Kaiser
2001-02-06 20:17             ` John Fremlin
2001-02-24 13:59 ` Ralf Baechle
2001-02-26 11:32   ` Robert Kaiser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30 18:58 mirabilos
2001-01-31  3:27 ` John R Lenton
2001-02-02 14:48 ` Pavel Machek

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=Pine.LNX.4.21.0102261204240.9294-100000@dagobert.svc.sysgo.de \
    --to=rob@sysgo.de \
    --cc=eccesys@topmail.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@uni-koblenz.de \
    /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).