From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [CFT] faster athlon/duron memory copy implementation
Date: Fri, 25 Oct 2002 02:10:23 +0200 [thread overview]
Message-ID: <20021025001023.GD3933@merlin.emma.line.org> (raw)
In-Reply-To: <3DB82ABF.8030706@colorfullife.com>
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 24 Oct 2002, Manfred Spraul wrote:
> AMD recommends to perform memory copies with backward read operations
> instead of prefetch.
>
> http://208.15.46.63/events/gdc2002.htm
>
> Attached is a test app that compares several memory copy implementations.
> Could you run it and report the results to me, together with cpu,
> chipset and memory type?
>
> Please run 2 or 3 times.
Here you are, three runs, shown is: floor((n1+n2+n3)/3)
where n_i is the results (cycles/page) of the i-th run of the respective test
Duron 700, Via KT133, PC133 (manuf. date 12/2000): (machine was NOT idle)
'warm up run' 11445
'2.4 non MMX' 22374
'2.4 MMX fallback' 20075
'2.4 MMX version' 17611
'faster_copy' 11103
'even_faster' 7225
'no_prefetch' 6549
Athlon XP1600+, Via KT333, PC2100 (manuf. date 10/2002): (idle)
'warm up run' 14106
'2.4 non MMX' 15382
'2.4 MMX fallback' 15416
'2.4 MMX version' 14103
'faster_copy' 8793
'even_faster' 8797
'no_prefetch' 6351
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iQCVAwUBPbiL5ydEoB0mv1ypAQEmpAP/UDkcx+UnItqTVcQzec3zDIUmrznZHkwa
0+cVgeMjg3e0QwIX85bmioicKlIw4WNz+AJZOyasFA+5VbxPBghkEkFOLzIzI9Bh
Eq2/uGNWrcwLfhIhsVgy0c/XgYLFoCY7mfH2oSs8+3TvIXIxhJoz7CsnaF+STk8e
wkWHfLN2+B0=
=4cF6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-25 0:04 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 17:15 Manfred Spraul
2002-10-24 17:37 ` Robert Love
2002-10-24 18:05 ` Zach Brown
2002-10-24 17:41 ` Andreas Steinmetz
2002-10-24 17:48 ` Matthias Welk
2002-10-24 19:01 ` erich
2002-10-24 19:11 ` Arjan van de Ven
2002-10-24 19:38 ` Manfred Spraul
2002-10-25 0:59 ` Panagiotis Papadakos
2002-10-24 17:53 ` Roger Luethi
2002-10-24 18:10 ` Daniel Egger
2002-10-24 19:15 ` Florin Iucha
2002-10-24 19:28 ` Manfred Spraul
2002-10-24 19:38 ` Dave Jones
2002-10-24 19:43 ` Ken Witherow
2002-10-25 13:08 ` Daniel Egger
2002-10-24 18:17 ` Eric Lammerts
2002-10-24 18:26 ` David Rees
2002-10-24 18:35 ` Josh McKinney
2002-10-24 18:36 ` Dave Jones
2002-10-24 18:43 ` Simon Fowler
2002-10-24 18:50 ` Simon Fowler
2002-10-24 18:56 ` Dave Jones
2002-10-24 18:48 ` Ernst Herzberg
2002-10-24 20:09 ` Ed Sweetman
2002-10-24 20:13 ` Robert Love
2002-10-24 20:31 ` Ed Sweetman
2002-10-24 20:49 ` Dave Jones
2002-10-24 20:26 ` Dave Jones
2002-10-25 9:19 ` Måns Rullgård
2002-10-24 19:11 ` Marcus Libäck
2002-10-24 19:19 ` Brian Gerst
2002-10-24 19:31 ` Matthias Schniedermeyer
2002-10-24 19:33 ` Pascal Schmidt
2002-10-24 19:39 ` Olaf Dietsche
2002-10-24 20:27 ` Mike Civil
2002-10-24 20:44 ` Willy TARREAU
2002-10-24 21:46 ` Josh Fryman
2002-10-24 22:18 ` Tim Schmielau
2002-10-24 23:09 ` Hirokazu Takahashi
2002-10-24 23:37 ` Ryan Cumming
2002-10-25 0:10 ` Matthias Andree [this message]
2002-10-25 8:35 ` venom
2002-10-25 13:31 ` Denis Vlasenko
2002-10-26 12:11 ` Jurjen Oskam
2002-10-24 18:27 Shawn Starr
2002-10-24 20:51 Dieter Nützel
2002-10-24 21:01 ` Dieter Nützel
2002-10-24 21:16 ` Willy TARREAU
2002-10-24 22:01 Harm Verhagen
2002-10-25 16:29 Jorge Bernal "Koke"
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=20021025001023.GD3933@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome