linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Surda <shurdeek@panorama.sth.ac.at>
To: linux-kernel@vger.kernel.org
Subject: Re: memcpy to videoram eats too much CPU on ATI cards (cache trashing?)
Date: Tue, 28 Aug 2001 00:01:27 +0200	[thread overview]
Message-ID: <20010828000127.M17545@shurdeek.cb.ac.at> (raw)
In-Reply-To: <E15bRy4-0004Va-00@the-village.bc.nu> <200108272140.XAA20798@cave.bitwizard.nl>
In-Reply-To: <200108272140.XAA20798@cave.bitwizard.nl>; from R.E.Wolff@BitWizard.nl on Mon, Aug 27, 2001 at 11:40:44PM +0200

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

On Mon, Aug 27, 2001 at 11:40:44PM +0200, Rogier Wolff wrote:
> However, as the X server manages to finish doing what it has to do before
> the next timer tick, it will almost never get a timer tick accounted to it.
Yes, I also realised that, and other people also seem to think it is this way.

So the conclusion is basically that the card can't chew data that fast and I
should use busmastering instead of memcpy (and other drivers should do that
too because "hidden load" occurs anyway). I'm working on it.

Thanks to all who replied, I am as always pleased by the cooperation in
open-source world and wish everyone good luck. Yeah, and linux rocks of course
:-)

> 			Roger. 
Bye,

Peter Surda (Shurdeek) <shurdeek@panorama.sth.ac.at>, ICQ 10236103, +436505122023

--
               I believe the technical term is "Oops!"

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-08-27 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 18:13 memcpy to videoram eats too much CPU on ATI cards (cache trashing?) Peter Surda
2001-08-27 19:22 ` Alan Cox
2001-08-27 21:40   ` Rogier Wolff
2001-08-27 22:01     ` Peter Surda [this message]
2001-09-06  6:18       ` (solved) memcpy to videoram eats too much CPU on ATI cards Peter Surda
2001-09-06 11:37       ` Daniel Egger
2001-09-06 13:10         ` Peter Surda

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=20010828000127.M17545@shurdeek.cb.ac.at \
    --to=shurdeek@panorama.sth.ac.at \
    --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;
as well as URLs for NNTP newsgroup(s).