From: Otto Solares <solca@guug.org>
To: Dan Malek <dan@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.4.x vs 2.6.x performance
Date: Wed, 25 Jan 2006 12:41:38 -0600 [thread overview]
Message-ID: <20060125184138.GA12874@guug.org> (raw)
In-Reply-To: <c8c05211d33576b79dee80725822322b@embeddedalley.com>
On Wed, Jan 25, 2006 at 07:45:38AM -0800, Dan Malek wrote:
> I wouldn't say "considerably" slower, but there are some
> performance differences. It's most evident on the
> smaller, slower processors, like the 8xx, but we have
> taken steps to alleviate that. The problem is 2.6 is just
> bigger with more stuff in it. You want the new features,
> you have to pay for that somewhere. I think it would
> help if the kernel was a little more configurable for
> embedded systems. It seems there is just too much
> stuff in a basic kernel that I wish could be stripped out.
Many things can be stripped out with LinuxTiny patches:
http://www.selenic.com/linux-tiny/
-otto
next prev parent reply other threads:[~2006-01-25 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 4:24 2.4.x vs 2.6.x performance Frank
2006-01-25 15:45 ` Dan Malek
2006-01-25 15:55 ` Frank
2006-01-25 18:41 ` Otto Solares [this message]
2006-01-25 20:14 ` Carlos Munoz
2006-01-25 23:46 ` Frank
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=20060125184138.GA12874@guug.org \
--to=solca@guug.org \
--cc=dan@embeddedalley.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.