mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roberto Jung Drebes <drebes@inf.ufrgs.br>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Athlon bug stomper. Pls apply.
Date: Wed, 19 Sep 2001 19:55:04 -0300 (EST)	[thread overview]
Message-ID: <Pine.GSO.4.21.0109191946550.1374-100000@jacui> (raw)
In-Reply-To: <Pine.LNX.4.30.0109191509480.29421-100000@anime.net>

On Wed, 19 Sep 2001, Dan Hollis wrote:

> We definitely need more data points too. So far we dont have any athlon.c
> data for kt133a with the bit on and off, only kt133.

My system is a kt133a, that show the bug. I have run a hundred tests,
first in a Athlon optimized kernel with the patch (55.7=0) then with a non
optimized kernel (55.7=1).

Here are some typical results:

K7 optimized:
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 19862 cycles per page
clear_page function '2.4 non MMX'        took 12296 cycles per page
clear_page function '2.4 MMX fallback'   took 12068 cycles per page
clear_page function '2.4 MMX version'    took 14936 cycles per page
clear_page function 'faster_clear_page'  took 4393 cycles per page
clear_page function 'even_faster_clear'  took 4362 cycles per page

copy_page() tests 
copy_page function 'warm up run'         took 22513 cycles per page
copy_page function '2.4 non MMX'         took 26280 cycles per page
copy_page function '2.4 MMX fallback'    took 26275 cycles per page
copy_page function '2.4 MMX version'     took 22537 cycles per page
copy_page function 'faster_copy'         took 10983 cycles per page
copy_page function 'even_faster'         took 11122 cycles per page

and here without:
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 12871 cycles per page
clear_page function '2.4 non MMX'        took 12325 cycles per page
clear_page function '2.4 MMX fallback'   took 12586 cycles per page
clear_page function '2.4 MMX version'    took 12021 cycles per page
clear_page function 'faster_clear_page'  took 4401 cycles per page
clear_page function 'even_faster_clear'  took 4370 cycles per page

copy_page() tests 
copy_page function 'warm up run'         took 19568 cycles per page
copy_page function '2.4 non MMX'         took 25353 cycles per page
copy_page function '2.4 MMX fallback'    took 25316 cycles per page
copy_page function '2.4 MMX version'     took 19541 cycles per page
copy_page function 'faster_copy'         took 11052 cycles per page
copy_page function 'even_faster'         took 10785 cycles per page

I thought that when I run the program in the non-optimized kernel with
55.7=1, the program was supposed to crash the system, but it doesn't seem
to do. Isn't the program the K7 optimized fast_copy_page()? Weird.

--
Roberto Jung Drebes <drebes@inf.ufrgs.br>
Porto Alegre, RS - Brasil
http://www.inf.ufrgs.br/~drebes/


  parent reply	other threads:[~2001-09-19 22:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2001-09-21 17:22     ` bill davidsen
2001-09-21 19:13       ` Dan Hollis
2001-09-19 20:52 ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2001-09-20 13:08 Petr Vandrovec
2001-09-19 23:33 Leif Sawyer
2001-09-19 14:31 Re[2]: " Liakakis Kostas
2001-09-19 14:43 ` Stefan Smietanowski
2001-09-19 13:47 Re[2]: " Thomas Langås
2001-09-19 14:55 ` Jan Niehusmann
2001-09-19 16:00   ` Linus Torvalds
2001-09-19 17:15     ` safemode
2001-09-19 18:22       ` Stefan Smietanowski
2001-09-19 18:43     ` Re[2]: " 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         ` Vojtech Pavlik
2001-09-19 20:57           ` Dan Hollis
2001-09-19 21:29             ` Vojtech Pavlik
2001-09-19 23:23         ` Luigi Genoni
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-20  9:03       ` VDA
2001-09-20  0:19     ` Re[2]: " Nicholas Knight
2001-09-20  1:27       ` Stefan Smietanowski
2001-09-18 14:51 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-23 23:33 ` Jan Niehusmann
2001-09-24 15:44   ` bill davidsen

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=Pine.GSO.4.21.0109191946550.1374-100000@jacui \
    --to=drebes@inf.ufrgs.br \
    --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

all inboxes | Powered by JetHome®