mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: porter@cox.net, davem@redhat.com, giduru@yahoo.com,
	andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: RE:Re: The end of embedded Linux?
Date: Mon, 7 Oct 2002 17:21:51 +0100	[thread overview]
Message-ID: <0fc4721201607a2DTVMAIL5@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

Suggesting a entire new sub config option seems wise, in this way not only arm ipaqs could benefit, so could 386s , whole series of rejuvinated computers, become useful.

Cheers, Dean.

On 	Mon, 7 Oct 2002 09:22:12 -0700 	Matt Porter <porter@cox.net> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 3451 bytes --]

From: Matt Porter <porter@cox.net>
To: "David S. Miller" <davem@redhat.com>
Cc: giduru@yahoo.com, andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: The end of embedded Linux?
Date: Mon, 7 Oct 2002 09:22:12 -0700
Message-ID: <20021007092212.B18610@home.com>

On Sat, Oct 05, 2002 at 09:28:32PM -0700, David S. Miller wrote:
> Embedded applications tend to have issues which are entirely specific
> to that embedded project.  As such, those are things that do not
> belong in a general purpose OS.

Exactly, every application wants some of the finer details of
kernel operation tuned to their task.

> The common areas, like smaller hashtables or whatever, sure put a
> CONFIG_SMALL_KERNEL option in there and start submitting the
> one-liners here and there that do it.

Ahhh, but you just defeated the ideal of being able to customize
to task.  This is where the hallowed "the user is dumb" theory
bites us in the ass.  A single option to control all these sizing
issues reduces flexibility and that is what the embedded system
designer is looking for.  The ideal situation is if as we work
on all these areas where we can reduce size, we provide fine
grained options to tweak them (with a default desktop/server value
and a default "tiny" value).  You can have this CONFIG_TINY or
whatever, but then we should also provide the ability to tweak
the values exactly how we want in a specific application.  The
tweaking options can be buried under advanced kernel options
with the appropriate disclaimers about shooting yourself in
the foot.

Regards,
-- 
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2002-10-07 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 16:21 Hell.Surfers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-09 14:28 Hell.Surfers
2002-10-09 14:11 Hell.Surfers
2002-10-08 23:10 Hell.Surfers
2002-10-08 22:28 Hell.Surfers
2002-10-08 21:52 Hell.Surfers
2002-10-08 16:32 Hell.Surfers
2002-10-08 16:27 ` David Lang
2002-10-08 13:01 Hell.Surfers
2002-10-08  9:51 Hell.Surfers
2002-10-08 14:22 ` Gerhard Mack
2002-10-07 11:47 Hell.Surfers

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=0fc4721201607a2DTVMAIL5@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=andre@linux-ide.org \
    --cc=davem@redhat.com \
    --cc=giduru@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=porter@cox.net \
    /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

all inboxes | Powered by JetHome®