public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthew S . Hallacy" <poptix@techmonkeys.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Wed, 5 Sep 2001 03:59:10 -0600	[thread overview]
Message-ID: <20010905035910.L20505@techmonkeys.org> (raw)
In-Reply-To: <200109050521.WAA26155@equinox.unr.edu>
In-Reply-To: <200109050521.WAA26155@equinox.unr.edu>; from ejolson@unr.edu on Tue, Sep 04, 2001 at 10:21:58PM -0700

On Tue, Sep 04, 2001 at 10:21:58PM -0700, Eric Olson wrote:
> 
> Robert Redelmeier told me he has written a version of his burnMMX which 
> uses K7 MMX 3DNow streaming cache bypass load/store instruction sequences
> similar to what is used in linux/arch/i386/lib/mmx.c
> 

I'm happy to report that after leaving these (burnK7, and burnMMX) running for about 
30 minutes there were no problems, a slight increase in CPU/system temperature, but 
within safe limits, along with a nice load average.. FYI:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 4
cpu MHz         : 1327.702
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips        : 2647.65

note this is the "c" core chip,
256M DDR RAM,
PC Chips M830LR motherboard w/ the SiS 735 Chipset,
(note, my single-chip chipset requires no fan, unlike the VIA chipsets)

All rather well considering the CPU fan is missing two blades, and only has the little
pink patch of thermal grease.



				Matthew S. Hallacy

-- 

  reply	other threads:[~2001-09-05  9:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05  5:21 Athlon doesn't like Athlon optimisation? Eric Olson
2001-09-05  9:59 ` Matthew S . Hallacy [this message]
2001-09-05 15:56 ` David Hollister
  -- strict thread matches above, loose matches on Subject: below --
2001-09-23 10:04 Jim Blomo
2001-09-07  7:33 Jim Blomo
2001-09-07  8:00 ` Dan Hollis
2001-09-07  8:39 ` Andrzej Krzysztofowicz
2001-09-07 17:25   ` Mike Fedyk
2001-09-05 18:37 Eric Olson
2001-09-05 14:22 noneuclidean
2001-09-05 17:37 ` Simen Thoresen
2001-09-05 18:07 ` Dan Hollis
2001-09-03  8:13 Eric Olson
2001-09-03 15:55 ` Ghozlane Toumi
2001-09-04 10:19   ` Dan Hollis
2001-09-04  9:35 ` Matthew S . Hallacy
     [not found] <fa.kt7mv6v.qiq718@ifi.uio.no>
     [not found] ` <fa.j3okgqv.lmova7@ifi.uio.no>
2001-08-31 12:11   ` Dan Maas
2001-08-31  2:42 Jan Niehusmann
2001-08-31  3:07 ` David Hollister
2001-08-31  3:34   ` Albert D. Cahalan
2001-08-31  3:50     ` Richard Gooch
2001-08-31  4:20     ` Dan Hollis
2001-08-31  5:05       ` Chris Abbey
2001-08-31  8:27         ` Arjan van de Ven
2001-08-31  9:36           ` Nicholas Knight
2001-08-31 14:17           ` David Hollister
2001-08-31  6:02       ` Paul G. Allen
2001-08-31  6:15         ` Steven Spence
2001-08-31 14:06         ` Alan Cox
2001-08-31  9:21       ` Phillip Susi
2001-08-31 14:00       ` Alan Cox
2001-08-31 20:37         ` Dan Hollis
2001-08-31 20:53           ` Alan Cox
2001-09-08 18:01             ` Eric W. Biederman
2001-08-31 20:53           ` Mike Fedyk
2001-08-31  8:08   ` Joerg Plate
2001-08-31 18:18   ` Tim Moore
2001-08-31 19:17     ` Bobby D. Bryant
2001-08-31 19:43       ` Tim Moore
2001-09-01 10:06   ` Jim Roland
2001-09-01 12:04     ` Joerg Plate
2001-09-01 14:39     ` David Hollister
2001-09-01 15:50       ` Alan Cox
2001-09-01 16:27         ` David Hollister
2001-09-03  8:03       ` Jim Roland

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=20010905035910.L20505@techmonkeys.org \
    --to=poptix@techmonkeys.org \
    --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