mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: j4K3xBl4sT3r <jakexblaster@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Which kernel is the best for a small linux system?
Date: Mon, 13 Mar 2006 21:18:12 -0300	[thread overview]
Message-ID: <436c596f0603131618s1fb4b37bre70d66712a6d29b7@mail.gmail.com> (raw)
In-Reply-To: <20060313190109.GC13973@stusta.de>

On 3/13/06, Adrian Bunk <bunk@stusta.de> wrote:
> On Mon, Mar 13, 2006 at 01:41:27PM -0500, Lee Revell wrote:
> > On Mon, 2006-03-13 at 19:27 +0100, Sam Ravnborg wrote:
> > > # latencies up to 80% slower
> >
> > This is certainly bullshit, it has not been true since 2.6.7 or so.
> >
> > Did not visit the page but that list smells like they are selling
> > something.
>
> The might be issues already fixed in 2.6.15 (he tested the then-current
> 2.6.11.7) or there might be powerpc specific problems, but after a quick
> look at this page it looks like a serious page.
>
> He also posted the complete lmbench results, dmesg's and .config's at
> his page, and from a first view I'd say he has very well documented
> what and how he measured.
>
> > Lee
>
> cu
> Adrian
>
> --
>
>        "Is there not promise of rain?" Ling Tan asked suddenly out
>         of the darkness. There had been need of rain for many days.
>        "Only a promise," Lao Er said.
>                                        Pearl S. Buck - Dragon Seed
>
>

Ye, I just compiled the lastest kernel, 2.6.15.6, it seems a lot
faster than my old one, 2.6.15.4, with the same configuration, and
faster to compile, even I was compiling dietlibc (that incredible got
only 10MB).

  reply	other threads:[~2006-03-14  0:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  0:40 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 [this message]
2006-03-13 19:08     ` Diego Calleja
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=436c596f0603131618s1fb4b37bre70d66712a6d29b7@mail.gmail.com \
    --to=jakexblaster@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®