public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hollister <david@digitalaudioresources.org>
To: arjanv@redhat.com
Cc: Chris Abbey <linux@cabbey.net>, linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Fri, 31 Aug 2001 07:17:52 -0700	[thread overview]
Message-ID: <3B8F9C90.7080100@digitalaudioresources.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0108302117150.16904-100000@anime.net> <Pine.LNX.4.33.0108302353380.4964-100000@tweedle.cabbey.net> <3B8F4A64.8B9DEDE4@redhat.com>

Arjan van de Ven wrote:
> 
> For the upcomming Red Hat Linux release an athlon kernel
> will be included, and due to the people who have this
> problem, I added a kernel commandline option to disable
> the optimized page_copy() and clear_page() functions.
> The use of this option makes the machines, of the people
> who had this problem, happy again.
> 
> Now I also wrote the 2 functions in question, and I am
> very convinced that they are correct. They also work on
> the vast majority of motherboards, and most of the failure
> cases are cheaper motherboards (or cheap PSU's).

Hey look, folks.  I didn't point a finger and try to blame anybody or anything. 
  I'm as much a Linux advocate as the next guy.  Granted, I have not tried every 
trick under the sun to get it to work.  I don't really care that much.  I can 
live with my memory accesses taking a few microseconds longer.  My point, and my 
only point, to all this was just to add data.  If there's something relatively 
easy I can try, I will.  Otherwise, life goes on.
-- 
David Hollister
Driversoft Engineering:  http://devicedrivers.com
Digital Audio Resources: http://digitalaudioresources.org


  parent reply	other threads:[~2001-08-31 14:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  2:42 Athlon doesn't like Athlon optimisation? 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 [this message]
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
     [not found]       ` <l4nnm9.rqp.ln@schlich.user.dfncis.de>
2001-08-31 13:58         ` Athlon doesn't like Athlon optimisation? [PATCH] Radu-Adrian Feurdean
2001-08-31 14:00       ` Athlon doesn't like Athlon optimisation? 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
     [not found] <fa.kt7mv6v.qiq718@ifi.uio.no>
     [not found] ` <fa.j3okgqv.lmova7@ifi.uio.no>
2001-08-31 12:11   ` Dan Maas
  -- strict thread matches above, loose matches on Subject: below --
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
2001-09-05  5:21 Eric Olson
2001-09-05  9:59 ` Matthew S . Hallacy
2001-09-05 15:56 ` David Hollister
2001-09-05 14:22 noneuclidean
2001-09-05 17:37 ` Simen Thoresen
2001-09-05 18:07 ` Dan Hollis
2001-09-05 18:37 Eric Olson
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-23 10:04 Jim Blomo

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=3B8F9C90.7080100@digitalaudioresources.org \
    --to=david@digitalaudioresources.org \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@cabbey.net \
    /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