linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Speed tests - G4-400 and PIII-600
Date: Thu, 3 Feb 2000 18:28:21 +0100	[thread overview]
Message-ID: <20000203182821.009176@mailhost.mipsys.com> (raw)
In-Reply-To: <8525687A.0059AAA1.00@D51MTA03.pok.ibm.com>


On Thu, Feb 3, 2000,  <jlquinn@us.ibm.com> wrote:


>How intensive is the computation on the image?  If you are running through
>a large image with short computations at each pixel, you may be limited by
>memory bandwidth.  Both of those machines have 100Mhz busses, right?  In
>this case, you'd be roughly even at the start from a raw hardware viewpoint
>and then the fact that x86 tends to receive more optimization work in the
>compiler might push it into the lead.

Something else that can affect performances on PowerPC when doing large
quantities of data manipulations is the way datas are fetched/stored in
memory. I think Intel processors do a good job with byte and short
accesses while the PPC loves when everything is naturally aligned and all
accesses are done in 32 bits quantities. A bunch of pixel manipulation
code I've seen in the past few years tends to use byte access to the
pixel datas in memory. This can be very inefficient.

Unfortunately, most of the existing code is written by programmers that
either don't care or optimize for their x86 box...


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-03 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-03 16:19 Speed tests - G4-400 and PIII-600 jlquinn
2000-02-03 17:28 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-03 16:11 jlquinn
     [not found] <88732CD95EB64875C125687900681C6E.00681C98C1256879@kehl.dalim.de>
2000-02-03  8:34 ` Stephane GEORGES
2000-02-04  6:19   ` Timothy A. Seufert

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=20000203182821.009176@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.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).