From: Frank <frannk_m1@yahoo.com>
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 07:55:47 -0800 (PST) [thread overview]
Message-ID: <20060125155547.83082.qmail@web32207.mail.mud.yahoo.com> (raw)
In-Reply-To: <c8c05211d33576b79dee80725822322b@embeddedalley.com>
--- Dan MaleMalekn@daneembeddedalley> wrote:
>
> On Jan 22, 2006, at 8:24 PM, Frank wrote:
>
> > I remember reading a while back that the 2.6 kernel is
> > considerably slower
>
> 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.
>
> > I'm thinking about moving to 2.6 since a lot of open source
> > projects have stopped suposuporting 2.4 kernel.
>
> You know, this is a "community effort", not "when are you
> going to fix it for me" :-) Use 2.6, measure it using your
> application, and submit updates that improve it. Some of
> us have already done quite a bit, so do your part, too.
>
> Thanks.
>
> -- Dan
I wasn't implying problems with 2.6 kernel would preclude me
from using it and fixing problems. I just wanted to know what to
expect so I can adjust my schedule accordingly
Thanks for the reply...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-01-25 15:55 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 [this message]
2006-01-25 18:41 ` Otto Solares
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=20060125155547.83082.qmail@web32207.mail.mud.yahoo.com \
--to=frannk_m1@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).