All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: 82xx performance
Date: Tue, 15 Jul 2008 21:50:35 +0200	[thread overview]
Message-ID: <200807152150.35811.arnd@arndb.de> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B04AE6877@ismail.innsys.innovsys.com>

On Tuesday 15 July 2008, Rune Torgersen wrote:
> Using arch/ppc I got a 2.6.25 kernel to boot, and the kernel compile
> test I did is almost identical (within 1%) of what the arch/powerpc
> 2.6.25 did, so it seems to be a difference between 2.6.18 and 2.6.25
> (I'll see if I can find an exact version, as I think my ppc port can be
> compiled for all versions from 2.6.18 to 25)

You probably already know git-bisect, but if you don't, you should
definitely give it a try. It's the best tool to find which patch
exactly broke your performance.

	Arnd <><

  reply	other threads:[~2008-07-15 19:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 16:34 82xx performance Rune Torgersen
2008-07-14 20:44 ` Arnd Bergmann
2008-07-15 14:16   ` Rune Torgersen
2008-07-15 18:25   ` Rune Torgersen
2008-07-15 19:50     ` Arnd Bergmann [this message]
2008-07-16 21:08       ` Rune Torgersen
2008-07-16 21:45         ` Arnd Bergmann
2008-07-16 21:53           ` Rune Torgersen
2008-07-16 22:32             ` Arnd Bergmann
2008-07-17 15:12               ` Rune Torgersen
2008-07-17 15:47                 ` Arnd Bergmann
2008-07-17 15:52                   ` Rune Torgersen
2008-07-17 18:24                   ` Rune Torgersen
2008-07-17 19:43                     ` Arnd Bergmann
2008-07-17 19:54                       ` Rune Torgersen
2008-07-17 21:32                         ` Arnd Bergmann
2008-07-25 20:41                           ` Rune Torgersen
2008-07-26  3:47                             ` Milton Miller
2008-07-15 15:57 ` Milton Miller
2008-07-15 18:12   ` Rune Torgersen

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=200807152150.35811.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 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.