public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: arjan@infradead.org, jakexblaster@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Which kernel is the best for a small linux system?
Date: Mon, 13 Mar 2006 20:08:27 +0100	[thread overview]
Message-ID: <20060313200827.71968d82.diegocg@gmail.com> (raw)
In-Reply-To: <20060313182725.GA31211@mars.ravnborg.org>

El Mon, 13 Mar 2006 19:27:25 +0100,
Sam Ravnborg <sam@ravnborg.org> escribió:

> Any comments on this:
> http://www.denx.de/wiki/Know/Linux24vs26
> 
> On another denx.de page I found this summary (so you do not have to
> visit the page):
> # slow to build: 2.6 takes 30...40% longer to compile
> # Big memory footprint in flash: the 2.6 compressed kernel image is
> # 30...40% bigger
> # Big memory footprint in RAM: the 2.6 kernel needs 30...40% more RAM;

In one of those analysis (2.6 sandpoint kernel) they didn't disable
CONFIG_KALLSYMS (they disabled it on the tqm860l though), that makes the
kernel way too big and should be disabled by embedded systems, I don't
understand. That one at least should be fixed, 2.4 didn't even feature
kallsyms.

Also, they claim that context switches are "on average 55% slower (range:
10...94%)", which may be very well a ppc-only bug (in x86 at least
system calls got much faster). And syscalls being much slower is why most
of the other microbenchmarks look so bad.


  parent reply	other threads:[~2006-03-13 19:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  0:40 Which kernel is the best for a small linux system? j4K3xBl4sT3r
2006-03-13  8:00 ` Lexington Luthor
2006-03-15  1:35   ` Grant Coady
2006-03-15  1:46     ` Randy.Dunlap
2006-03-13  8:17 ` Arjan van de Ven
2006-03-13 18:03   ` Grant Coady
2006-03-13 18:06     ` Arjan van de Ven
2006-03-14  6:21       ` Willy Tarreau
2006-03-14  7:29         ` Ingo Molnar
2006-03-14  8:18           ` Mike Galbraith
2006-03-14  9:05           ` Mike Galbraith
2006-03-14 15:54             ` Willy Tarreau
2006-03-16 15:24             ` Mike Galbraith
2006-03-14 10:03         ` Grant Coady
2006-03-14 22:21           ` Russell King
2006-03-15  0:46             ` Grant Coady
     [not found]               ` <20060315080313.GC3166@flint.arm.linux.org.uk>
2006-03-15  9:37                 ` Grant Coady
2006-03-15 22:53             ` Jan Engelhardt
2006-03-15 23:32               ` Grant Coady
2006-03-16  4:19                 ` Mike Galbraith
2006-03-16  8:12                   ` Mike Galbraith
2006-03-16  8:31                     ` Lee Revell
2006-03-16  8:55                       ` Mike Galbraith
2006-03-16  9:20                         ` Mike Galbraith
2006-03-16  2:55               ` Valdis.Kletnieks
2006-03-13 18:27   ` Sam Ravnborg
2006-03-13 18:41     ` Lee Revell
2006-03-13 19:01       ` Adrian Bunk
2006-03-14  0:18         ` j4K3xBl4sT3r
2006-03-13 19:08     ` Diego Calleja [this message]
2006-03-13 22:00     ` Pantelis Antoniou
2006-03-13 22:01       ` j4K3xBl4sT3r
2006-03-13 22:20         ` Pantelis Antoniou
2006-03-13 22:33           ` j4K3xBl4sT3r
2006-03-16 12:03             ` Pavel Machek
2006-03-13 22:25         ` Lee Revell
2006-03-14  3:53           ` Grant Coady
2006-03-15 22:57     ` Jan Engelhardt
2006-03-15 23:10       ` Adrian Bunk
2006-03-16 13:39         ` linux-os (Dick Johnson)

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=20060313200827.71968d82.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=arjan@infradead.org \
    --cc=jakexblaster@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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