public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Dan Hollis <goemon@anime.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Athlon bug stomper. Pls apply.
Date: Wed, 19 Sep 2001 22:36:26 +0200	[thread overview]
Message-ID: <20010919223626.B3775@suse.cz> (raw)
In-Reply-To: <9oafeu$1o0$1@penguin.transmeta.com> <Pine.LNX.4.30.0109191141560.24917-100000@anime.net> <3BA8EA04.E55BAA02@redhat.com>
In-Reply-To: <3BA8EA04.E55BAA02@redhat.com>; from arjanv@redhat.com on Wed, Sep 19, 2001 at 07:55:00PM +0100

On Wed, Sep 19, 2001 at 07:55:00PM +0100, Arjan van de Ven wrote:
> Dan Hollis wrote:
> > 
> > On Wed, 19 Sep 2001, Linus Torvalds wrote:
> > > It is _probably_ an undocumented performance thing, and clearing that
> > > bit may slow something down. But it might also change some behaviour,
> > > and knowing _what_ the behaviour is might be very useful for figuring
> > > out what it is that triggers the problem.
> > 
> > AFAIK noone has even tested it yet to see what it does to performance! Eg
> > it might slow down memory access so that athlon-optimized memcopy is now
> > slower than non-athlon-optimized memcopy. And if it turns out to be the
> > case, we might as well just use the non-athlon-optimized memcopy instead
> > of twiddling undocumented northbridge bits...
> 
> Ok but that part is simple:
> 
> run
> 
> http://www.fenrus.demon.nl/athlon.c

Here we go, a TBird 1.1G with KT133 (non-A), normally working with value
89 in reg 55, not exhibiting the bug under any setting.

with 89 (working, default):

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 20842 cycles per page
clear_page function '2.4 non MMX'        took 13737 cycles per page
clear_page function '2.4 MMX fallback'   took 14071 cycles per page
clear_page function '2.4 MMX version'    took 13269 cycles per page
clear_page function 'faster_clear_page'  took 5485 cycles per page
clear_page function 'even_faster_clear'  took 5611 cycles per page

copy_page() tests 
copy_page function 'warm up run'         took 20049 cycles per page
copy_page function '2.4 non MMX'         took 29783 cycles per page
copy_page function '2.4 MMX fallback'    took 29679 cycles per page
copy_page function '2.4 MMX version'     took 20173 cycles per page
copy_page function 'faster_copy'         took 12641 cycles per page
copy_page function 'even_faster'         took 12443 cycles per page

with 09 (working, set using "setpci -d 1106:0305 55=09"):

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 20763 cycles per page
clear_page function '2.4 non MMX'        took 13754 cycles per page
clear_page function '2.4 MMX fallback'   took 13771 cycles per page
clear_page function '2.4 MMX version'    took 13340 cycles per page
clear_page function 'faster_clear_page'  took 5578 cycles per page
clear_page function 'even_faster_clear'  took 5774 cycles per page

copy_page() tests 
copy_page function 'warm up run'         took 20415 cycles per page
copy_page function '2.4 non MMX'         took 29629 cycles per page
copy_page function '2.4 MMX fallback'    took 29509 cycles per page
copy_page function '2.4 MMX version'     took 20287 cycles per page
copy_page function 'faster_copy'         took 12626 cycles per page
copy_page function 'even_faster'         took 12587 cycles per page

So there is no noticeable difference. The values for 'even_faster' vary
between 10000 and 13000 between different runs with either setting of
register 55.

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2001-09-19 20:36 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18 14:51 [PATCH] Athlon bug stomper. Pls apply VDA
2001-09-18 15:43 ` Alan Cox
2001-09-20  4:56   ` Albert D. Cahalan
2001-09-18 17:45 ` Jeff Garzik
2001-09-18 21:39 ` Liakakis Kostas
2001-09-19 13:08   ` Re[2]: " VDA
2001-09-19 13:41     ` Liakakis Kostas
2001-09-19 13:47       ` Thomas Langås
2001-09-19 14:31         ` Liakakis Kostas
2001-09-19 14:43           ` Stefan Smietanowski
2001-09-19 14:55           ` Re[2]: " Jan Niehusmann
2001-09-19 14:57             ` Liakakis Kostas
2001-09-19 18:12               ` Alan Cox
2001-09-19 21:18                 ` Re[2]: [PATCH] VIA " Aaron Tiensivu
2001-09-19 23:04                   ` Roberto Jung Drebes
2001-09-19 23:41                     ` Nicholas Knight
2001-09-19 16:00             ` Re[2]: [PATCH] Athlon " Linus Torvalds
2001-09-19 17:15               ` safemode
2001-09-19 18:22                 ` Stefan Smietanowski
2001-09-19 23:41                 ` Re[2]: " Nicholas Knight
2001-09-20 15:10                   ` Marek Mentel
2001-09-19 18:43               ` Dan Hollis
2001-09-19 18:55                 ` Arjan van de Ven
2001-09-19 19:00                   ` Roberto Jung Drebes
2001-09-19 19:17                     ` Arjan van de Ven
2001-09-19 20:16                     ` Dan Hollis
2001-09-19 19:50                   ` Ignacio Vazquez-Abrams
2001-09-19 20:01                     ` Ignacio Vazquez-Abrams
2001-09-19 20:40                       ` Ignacio Vazquez-Abrams
2001-09-19 21:43                         ` safemode
2001-09-19 22:22                           ` Brad Pepers
2001-09-19 22:28                             ` Erno Kuusela
2001-09-19 20:36                   ` Simen Thoresen
2001-09-19 20:37                     ` Dan Hollis
2001-09-19 20:51                       ` Simen Thoresen
2001-09-19 23:00                         ` Roberto Jung Drebes
2001-09-19 20:36                   ` Vojtech Pavlik [this message]
2001-09-19 20:57                     ` Dan Hollis
2001-09-19 21:29                       ` Vojtech Pavlik
2001-09-19 23:23                   ` Luigi Genoni
2001-09-20  9:03                   ` VDA
2001-09-19 18:58                 ` Re[2]: " Roberto Jung Drebes
2001-09-19 20:35                 ` Athlon bug stomper: perf. results brian
2001-09-19 20:30                   ` Dan Hollis
2001-09-19 22:14                     ` brian
2001-09-19 22:08                       ` Dan Hollis
2001-09-21  0:46                 ` Re[2]: [PATCH] Athlon bug stomper. Pls apply Pavel Machek
2001-09-20  0:19               ` Nicholas Knight
2001-09-20  1:27                 ` Stefan Smietanowski
2001-09-20  9:54                 ` Re[2]: " Liakakis Kostas
2001-09-19 23:04             ` Luigi Genoni
2001-09-19 14:05       ` Tom Diehl
2001-09-23 23:33 ` Jan Niehusmann
2001-09-24 15:44   ` bill davidsen
  -- strict thread matches above, loose matches on Subject: below --
2001-09-19 21:15 Petr Vandrovec
2001-09-19 19:21 ` Arjan van de Ven
2001-09-19 19:51   ` Dan Hollis
2001-09-19 19:59     ` Arjan van de Ven
2001-09-19 21:44     ` Eric W. Biederman
2001-09-19 22:13       ` Dan Hollis
2001-09-19 22:49         ` John Alvord
2001-09-19 23:14           ` Dan Hollis
2001-09-19 23:32             ` Daniel T. Chen
2001-09-19 22:55         ` Roberto Jung Drebes
2001-09-21 17:22     ` bill davidsen
2001-09-21 19:13       ` Dan Hollis
2001-09-19 20:52 ` Vojtech Pavlik
2001-09-19 23:33 Leif Sawyer
2001-09-20 13:08 Petr Vandrovec

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=20010919223626.B3775@suse.cz \
    --to=vojtech@suse.cz \
    --cc=arjanv@redhat.com \
    --cc=goemon@anime.net \
    --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