All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Fitzner <kfitzner@excelcia.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] B132L outperforms C160 - 64-bit userland needed?
Date: Tue, 16 Aug 2005 18:03:35 -0600	[thread overview]
Message-ID: <43027ED7.10007@excelcia.org> (raw)
In-Reply-To: <200508160800.29307.mszick@morethan.org>

Michael S. Zick wrote:

>>When that produced even worse results, I tried -march=2.0 vs 1.1 and
>>-mschedule=8000 vs 7300 seperately.  Each one alone slows down the
>>benchmark and the effect is addititive.  It seems that in Linux, right
>>now at least, compiling with -march=2.0 or -mschedule=8000 is a Bad Thing.
>>
> 
> It would be interesting to see if this also holds with a newer GCC.
> (3.4, 4.0, 4.1)

I can't see how it would be different.  Isn't compiling for PA2.0/8000
in Linux tying of GCC's hands behind its back.  You're telling it you
want good code for a 64-bit CPU, but it can't produce 64-bit code.

Is there any real possibility that this is compiler-related and not
simply a 32 vs. 64 bit issue?  If there is a real chance of this, I'll
bite the bullet and actually test out newer GCC versions.

> Try the same version kernel on both machines - you might just be seeing
> the difference between 2.6.8 and 2.6.10. (or 32bit and 64bit kernels).

I've installed 2.6.8.1 on the C160 to match the B132L.  I'm seeing a 2%
increase in speed across the board with the different kernel.  I
attribute this to my having set the CPU to 7300 in the kernel settings.
 The speed increase is exactly consistent with the difference I see in
executables on my C160 when compiled with -march1.1/-mschedule=7300
rather than 2.0/8000.  The C160 still underperforms significantly when
compared to the B132L.

I have not yet compiled a 64-bit kernel for my C160.  All advice I have
read is that this is a complete waste of time since without a 64-bit
userland it will just make the kernel bigger and slower.  Is there
likely to be any benefit at all to a 64-bit kernel?

> Also, what compiler was used to build the kernel.

Same as used to build nBench, gcc 3.3.5 (Debian 1:3.3.5-13).

	Kurt.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-08-17  0:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  9:23 [parisc-linux] B132L outperforms C160 - 64-bit userland needed? Kurt Fitzner
2005-08-16 13:00 ` Michael S. Zick
2005-08-17  0:03   ` Kurt Fitzner [this message]
2005-08-17  1:32     ` John David Anglin
2005-08-17  1:48       ` Michael S. Zick
2005-08-17  3:43       ` Kurt Fitzner
2005-08-17  6:37         ` Grant Grundler
2005-08-17 14:16         ` John David Anglin
2005-08-17  6:19 ` Grant Grundler
2005-08-17 18:42   ` Kurt Fitzner
2005-08-17 18:56     ` Kyle McMartin
2005-08-17 19:40     ` Andrew Sharp
2005-08-18  5:27       ` Kurt Fitzner
2005-08-18  7:17         ` Grant Grundler
2005-08-20  6:21         ` Grant Grundler
2005-08-17 20:38   ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2005-08-18  8:27 Joel Soete
2005-08-20  6:26 ` Grant Grundler
     [not found]   ` <430778F2.8020406@tiscali.be>
     [not found]     ` <20050820234126.GA20524@colo.lackof.org>
2005-08-21  9:42       ` Joel Soete
     [not found]       ` <20050820235516.GE2756@parcelfarce.linux.theplanet.co.uk>
2005-08-21 10:29         ` Joel Soete
2005-08-21 14:19           ` Matthew Wilcox

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=43027ED7.10007@excelcia.org \
    --to=kfitzner@excelcia.org \
    --cc=parisc-linux@lists.parisc-linux.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.