From: Disconnect <lkml@sigkill.net>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, arjan@fenrus.demon.nl
Subject: Re: Athlon problem report summary
Date: Sat, 21 Apr 2001 11:07:17 -0400 [thread overview]
Message-ID: <20010421110717.A5804@sigkill.net> (raw)
In-Reply-To: <20010420203029.C20176@sigkill.net> <E14qlMO-0002bj-00@the-village.bc.nu>
In-Reply-To: <E14qlMO-0002bj-00@the-village.bc.nu>
> I wrote a set of programs to tune the MMX code. Arjan I suspect did similar
> when he reoptimised the code for the newer Athlon. Simple stuff like
Alan - your proggy ran (no output) for about 5 seconds or so, then exited.
Arjan - from yours, I get the results below. Either way, no OOPs, no
errors, etc. (Felt pretty silly as I remounted all my drives and brought
it back up to multi-user mode ;) ..)
So am I correct in assuming at this point that MMX is working fine on this
mobo/chip combo? What's next?
Athlon test program $Id: fast.c,v 1.6 2000/09/23 09:05:45 arjan Exp $
clear_page() tests
clear_page function 'warm up run' took 16151 cycles per page
clear_page function '2.4 non MMX' took 11893 cycles per page
clear_page function '2.4 MMX fallback' took 11736 cycles per page
clear_page function '2.4 MMX version' took 10436 cycles per page
clear_page function 'faster_clear_page' took 4998 cycles per page
clear_page function 'even_faster_clear' took 4881 cycles per page
copy_page() tests
copy_page function 'warm up run' took 17595 cycles per page
copy_page function '2.4 non MMX' took 26701 cycles per page
copy_page function '2.4 MMX fallback' took 26708 cycles per page
copy_page function '2.4 MMX version' took 17649 cycles per page
copy_page function 'faster_copy' took 10480 cycles per page
copy_page function 'even_faster' took 10464 cycles per page
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5---
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2001-04-21 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fkfenov.14jqeov@ifi.uio.no>
2001-04-16 12:30 ` Athlon problem report summary Alan Cox
2001-04-16 12:33 ` Alan Cox
2001-04-16 13:17 ` Kurt Roeckx
2001-04-20 23:52 ` Disconnect
2001-04-21 0:14 ` Alan Cox
2001-04-21 0:22 ` Disconnect
2001-04-21 0:28 ` Alan Cox
2001-04-21 0:30 ` Disconnect
2001-04-21 0:34 ` Alan Cox
2001-04-21 9:27 ` Arjan van de Ven
2001-04-21 15:07 ` Disconnect [this message]
[not found] ` <fa.fn57bnv.nno4p4@ifi.uio.no>
2001-04-21 2:54 ` Jeff Lightfoot
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=20010421110717.A5804@sigkill.net \
--to=lkml@sigkill.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.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.