linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddedalley.com>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Stable Linux kernel 2.6 for MPC8XX
Date: Fri, 10 Mar 2006 08:16:10 -0500	[thread overview]
Message-ID: <da161c5383a7c1645080b918b0fd30ef@embeddedalley.com> (raw)
In-Reply-To: <200603100822.42764.david.jander@protonic.nl>


On Mar 10, 2006, at 2:22 AM, David Jander wrote:

> I believe most of those observations and measurements are not valid 
> anymore.
> Kernel 2.6 for 8xx has come a long way since this article was written.

They are still valid, we just have more knowledge about how to
configure the kernels and have added some features you can
use to mitigate the performance issues.  The Linux 2.6 kernel
is simply bigger than 2.4, and on these small, resource challenged
processors, you need to very carefully configure the kernels to
your requirements.

Thanks.


	-- Dan

  reply	other threads:[~2006-03-10 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 14:29 Stable Linux kernel 2.6 for MPC8XX Fillod Stephane
2006-03-10  7:22 ` David Jander
2006-03-10 13:16   ` Dan Malek [this message]
2006-03-10 15:33   ` Wolfgang Denk
2006-03-14  7:50     ` David Jander
2006-03-14 11:56       ` Carlos Mitidieri
2006-03-14 14:01       ` Dan Malek
2006-03-14 14:58         ` David Jander
  -- strict thread matches above, loose matches on Subject: below --
2006-03-14  8:34 Wolfgang Grandegger
2006-03-14 14:46 ` David Jander
2006-02-28  8:50 Minor bug in file irq.h Laurent Lagrange
2006-03-08 14:32 ` Stable Linux kernel 2.6 for MPC8XX Laurent Lagrange

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=da161c5383a7c1645080b918b0fd30ef@embeddedalley.com \
    --to=dan@embeddedalley.com \
    --cc=david.jander@protonic.nl \
    --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).