From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Reading from /dev/fb0 very slow?
Date: Sun, 3 Jun 2001 00:46:55 +0200 [thread overview]
Message-ID: <20010603004655.E2434@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20010602105249.A979@bug.ucw.cz> <E156JUS-0002DC-00@the-village.bc.nu>
In-Reply-To: <E156JUS-0002DC-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Jun 02, 2001 at 11:03:24PM +0100
Hi!
> > I did some benchmarks, and my framebuffer is *way* faster when writing
> > than when reading:
>
> That is quite normal.
Unfortunately, at least X and few framebuffer modes can not survive
that too well.
vesafb ypan mode attempts to do video-to-video copy, which is slow.
Xserver attempts that, too.
> > That is 6 times slower! This is also very visible in X, where moving
> > regions is expensive, while just drawing regions is fast. For example
> > gnome-terminal is *way* faster *with* transparent background option.
> >
> > Any idea why such assymetry? [This is toshiba 4030cdt with vesafb and
> > 2.4.5]
>
> Writes to a PCI device can be queued or posted. Reads from a PCI device for
> obvious reasons have to stall the CPU until the data returns.
But they can't be posted indifinitely, right? I'm copying whole
framebuffer at a time, I do not believe PCI has enough buffers to
cache *that*. [Or is it using some kind of burst mode it can not use
for reading? That does not give a sense, you can cache reads, too....]
--
The best software in life is free (not shareware)! Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
next prev parent reply other threads:[~2001-06-02 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 8:52 Pavel Machek
2001-06-02 21:42 ` Jeff Garzik
2001-06-02 22:03 ` Alan Cox
2001-06-02 22:46 ` Pavel Machek [this message]
2001-06-02 22:49 ` Alan Cox
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=20010603004655.E2434@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--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
all inboxes | Powered by JetHome®