From: Felix Domke <tmbinc@elitedvb.net>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6 vs 2.4
Date: Fri, 12 May 2006 16:43:21 +0200 [thread overview]
Message-ID: <44649F09.2020803@elitedvb.net> (raw)
In-Reply-To: <82ecf08e0605120729l43041aebuaef375a568700354@mail.gmail.com>
Thiago Galesi wrote:
> Not much. This article is almost one year old. Even though some things
> do apply (like bigger footprint, etc), the kernel improved a lot on
> the months that followed that article.
> I've participated in a project that used a (somewhat patched) 2.6.10
> kernel, with soccessful results.
Can you point me to a list of changes which where done? I really like to
check if they apply to my performance problems with 2.6 kernels, i.e. if
it's worth porting the board specific changes to a newer kernel.
Felix
next prev parent reply other threads:[~2006-05-12 14:42 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
2006-05-12 14:23 ` Felix Domke
2006-05-12 14:29 ` Thiago Galesi
2006-05-12 14:43 ` Felix Domke [this message]
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=44649F09.2020803@elitedvb.net \
--to=tmbinc@elitedvb.net \
--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).