linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Srinivas Murthy <codevana@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6 vs 2.4
Date: Sat, 13 May 2006 00:02:02 +1000	[thread overview]
Message-ID: <1147442522.9412.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1147442231.9412.9.camel@localhost.localdomain>

On Fri, 2006-05-12 at 23:57 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2006-05-11 at 23:51 -0700, Srinivas Murthy wrote:
> > Hi,
> >  Wolfgang Denk has a good listing of issues to consider betn linux 2.4
> > vs 2.6 for ppc82xx based platforms
> > (http://www.denx.de/wiki/Know/Linux24vs26).
> >  
> >  Would this recommendation still hold?
> >  
> >  Are there any patches, developments in this area?
> 
> The main open question is: is somebody still maintaining the 8xx kernel
> port ?

Oh , and to give a better reply after reading that web page... I'd say
there might be a reason why 2.6 is slower (or appears slower) than 2.4
on some of those embedded platforms. It's definitely faster in a number
of areas on 6xx and other desktop CPUs. A lot of embedded folks will
then bitch and complain about the slowdown on their 8xx processor, but
very few of them if not none popped up actually identifying the actual
issues and coming up with solution for them during the 2.6 dev. cycle.

Ben.

  reply	other threads:[~2006-05-12 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  6:51 2.6 vs 2.4 Srinivas Murthy
2006-05-12 13:57 ` Benjamin Herrenschmidt
2006-05-12 14:02   ` Benjamin Herrenschmidt [this message]
2006-05-12 14:23   ` Felix Domke
2006-05-12 14:29 ` Thiago Galesi
2006-05-12 14:43   ` Felix Domke
2006-05-12 16:24     ` Thiago Galesi

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=1147442522.9412.12.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=codevana@gmail.com \
    --cc=linuxppc-dev@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).