From: Grant Grundler <grundler@parisc-linux.org>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] more cpup.c results
Date: Wed, 5 Jan 2005 09:02:14 -0700 [thread overview]
Message-ID: <20050105160214.GA24439@colo.lackof.org> (raw)
In-Reply-To: <1104914456.8221.34.camel@beavis>
On Wed, Jan 05, 2005 at 01:40:56AM -0700, Ryan Bradetich wrote:
> This is on a 64-bit kernel:
> $ uname -a
> Linux vega 2.6.10-pa3 #1 Sun Jan 2 14:28:36 MST 2005 parisc64 GNU/Linux
>
> TEST 1
> First Loop : min 9990 avg 11444 median 10352
> Later Loops : min 6290 avg 8673 median 8885
...
thanks for the results!
> This is on a 32-bit kernel:
> $ uname -a
> Linux vega 2.6.10-pa5 #1 Wed Jan 5 01:14:00 MST 2005 parisc GNU/Linux
>
> TEST 1
> First Loop : min 10924 avg 11555 median 11090
> Later Loops : min 7744 avg 8196 median 8130
> First Loop : min 9584 avg 10251 median 9790
> Later Loops : min 6451 avg 6836 median 6784
> First Loop : min 9487 avg 10104 median 9673
> Later Loops : min 6202 avg 6604 median 6550
Interesting that cpup3 is slightly faster than cpup2 with
the 32-bit kernel. Since user space is 32-bit always, I wouldn't
have expected a difference in "Later Loops" output.
> The K460 is a 8000 processor ... I'll see if I can get the K460
> installed and updated to give you results from that system as well. I
Well, don't sweat it. Others might have PA8000 box already up and running.
> am also working on getting you results from a 715/100
> as well (currently in the middle of a new debian install).
715 is PA1.1. cpup2/3 won't work there.
It would be worth trying variants of cpup0 (32-bit) scheduling
on PA1.1 machines. I'll leave that as an excercise for others.
thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-01-05 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050105055412.68E06495698@palinux.hppa>
2005-01-05 6:16 ` [parisc-linux] more cpup.c results Grant Grundler
2005-01-05 8:20 ` Joel Soete
2005-01-05 8:40 ` Ryan Bradetich
2005-01-05 16:02 ` Grant Grundler [this message]
[not found] ` <20050107095143.GN18497@tausq.org>
2005-01-09 19:07 ` [parisc-linux] pa_memcpy: 2 small question Joel Soete
2005-01-10 0:13 ` [parisc-linux] " Randolph Chung
2005-01-10 8:44 ` Joel Soete
2005-01-10 8:54 ` Randolph Chung
2005-01-10 17:12 ` Joel Soete
2005-01-10 17:17 ` Grant Grundler
2005-01-10 20:02 ` Stuart Brady
2005-01-11 18:14 ` Joel Soete
2005-01-12 1:49 ` Randolph Chung
2005-02-20 23:44 ` [parisc-linux] revisit copy_user_page_asm microbenchmarks Grant Grundler
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=20050105160214.GA24439@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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