public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aaron Tiensivu" <mojomofo@mojomofo.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Fri, 4 May 2001 18:26:14 -0400	[thread overview]
Message-ID: <006e01c0d4e9$3c0bd210$0300a8c0@methusela> (raw)
In-Reply-To: <E14vmpN-000822-00@the-village.bc.nu>


> What still stands out is that exactly _zero_ people have reported the same
> problem with non VIA chipset Athlons.

This might be grasping at straws I remember VIA problem in the "good old
days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write
settings that would cause issues like we're seeing with the Athlon
pre-fetches. This could be (total conjecture) related somehow to the
corruption bugs they are admitting to in the 686B although they are blaming
the SB Live now.




  reply	other threads:[~2001-05-04 22:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04 17:22 REVISED: Experimentation with Athlon and fast_page_copy Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26   ` Aaron Tiensivu [this message]
2001-05-04 18:10     ` Bobby D. Bryant
2001-05-05  6:43       ` John R Lenton
2001-05-05  7:20         ` Alan Cox
2001-05-07  1:26           ` John R Lenton
2001-05-07  1:30             ` Jeremy
2001-05-05  0:26     ` Joseph Carter
2001-05-05  3:51       ` Chris Wedgwood
2001-05-05  4:08         ` Seth Goldberg
     [not found]           ` <20010505163204.A29622@metastasis.f00f.org>
2001-05-05  5:03             ` Athlon and fast_page_copy: What's it worth ? :) Seth Goldberg
2001-05-05  6:20               ` Mark Hahn
2001-05-05  9:15                 ` Tom Leete
2001-05-05  7:17               ` Alan Cox
2001-05-05 14:19               ` Jonathan Morton
2001-05-05 14:41                 ` Alan Cox
2001-05-05 15:17                 ` Jonathan Morton
2001-05-08 21:16               ` Arjan van de Ven
2001-05-05  5:45         ` REVISED: Experimentation with Athlon and fast_page_copy Joseph Carter
2001-05-09  2:11   ` Tom Leete
2001-05-09  8:49     ` Alan Cox
2001-05-09 11:38       ` Tom Leete
2001-05-09 12:38         ` Alan Cox
2001-05-09 13:02           ` Tom Leete
  -- strict thread matches above, loose matches on Subject: below --
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15   ` Arjan van de Ven
2001-05-05  2:28 Dieter Nützel
2001-05-05  7:13 ` Alan Cox
2001-05-09 23:56   ` Dieter Nützel
2001-05-05 17:34 Jeremy

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='006e01c0d4e9$3c0bd210$0300a8c0@methusela' \
    --to=mojomofo@mojomofo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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