From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Peter Surda <shurdeek@panorama.sth.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: memcpy to videoram eats too much CPU on ATI cards (cach
Date: Mon, 27 Aug 2001 20:46:17 MET-1 [thread overview]
Message-ID: <1C537DA22F7@vcnet.vc.cvut.cz> (raw)
On 27 Aug 01 at 20:13, Peter Surda wrote:
>
> memcpy-ing 380kB at 25fps takes about 5ms per frame and causes X to eat 1% cpu
> time (time measurements were done by tsc)
> memcpy-ing 760kB at 25fps takes about 11ms per frame, but instead of eating
> 2% CPU time, it eats 35% (yes, that's 35 times more)
It is because of way how time accounting to processes works in Linux.
Your X-server gets time quantum, and starts copying data to videoram.
If it finishes before 1/HZ seconds, no consumed time is accounted to it.
As soon as task does not finish its job in 1/HZ seconds, some time is
accounted to it. Just try running some benchmark together with
your memcpy. You'll found that benchmark slowdown is (almost) linear with
memcpy size. Especially if you'll run benchmark on some nice level.
You can try varying size around 650-750kBs, and you'll find that it clibms
up very quickly in this range, just when consumed time crosses 10ms.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2001-08-27 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1C537DA22F7@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=shurdeek@panorama.sth.ac.at \
/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