Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Smith, Todd" <Todd.Smith@camc.org>
Cc: "'linux-mips@linux-mips.org '" <linux-mips@linux-mips.org>
Subject: Re: MIPS Kernel size
Date: Mon, 2 Feb 2004 19:53:29 +0100	[thread overview]
Message-ID: <20040202185329.GA23667@linux-mips.org> (raw)
In-Reply-To: <490E0430C3C72046ACF7F18B7CD76A2A56955D@KES.camcare.com>

On Mon, Feb 02, 2004 at 11:12:10AM -0500, Smith, Todd wrote:

> I am still interested in some older PDA usage that has limited resources.  I
> certainly don't want to hold up or stop current kernel dev but is there a
> problem with keeping small kernel and/or userspace limits?

Different tradeoffs.  In general the kernel is optimized for performance,
even at the cost of significant amounts of memory.  As the most infamous
example the kernel is using lots of fairly complex hash and radix trees.

But why would a system that has just a default route need the same kind
of data structures and algorithms it takes to route packets on backbone
router in the default free zone?  Why would you drive a moon rocket to
for shopping?

Linux has generally developped in the direction of larger machines and
higher scalability and sometimes that's causing fairly bad itching.  The
-tiny tree is an attempt to correct this.  It's a development tree but
with the goal of merging changes back into the standard kernel and I
hope much of it will be merged back into 2.6 - 2.8 is too far in the
future to wait for ...

  Ralf

  reply	other threads:[~2004-02-02 18:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 16:12 MIPS Kernel size Smith, Todd
2004-02-02 18:53 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02 21:48 Smith, Todd
2004-02-03 13:41 ` Maciej W. Rozycki
2004-02-03 15:17   ` Ralf Baechle
2004-02-03 14:50 ` Jan-Benedict Glaw
2004-02-03 15:18   ` Ralf Baechle
2004-02-03 16:52     ` Jan-Benedict Glaw
2004-02-03 17:07       ` Ralf Baechle
2004-02-03 15:16 ` Ralf Baechle
2004-01-27 14:51 kip.r2
2004-01-27 16:10 ` Thiemo Seufer
2004-02-02 14:09 ` Ralf Baechle
2004-02-02 18:43   ` Karsten Merker
2004-02-02 18:57     ` Ralf Baechle
2004-02-02 19:38       ` Geert Uytterhoeven
2004-02-02 19:46         ` Ralf Baechle
2004-02-02 19:50           ` Geert Uytterhoeven
2004-02-02 19:59             ` Ralf Baechle
2004-02-02 20:07               ` Thiemo Seufer
2004-02-02 20:32                 ` Ralf Baechle
2004-02-02 22:29         ` Peter Horton

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=20040202185329.GA23667@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Todd.Smith@camc.org \
    --cc=linux-mips@linux-mips.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