From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Blitter speed tests (was: smart blitter usage for scrolling)
Date: Fri, 11 May 2007 04:24:34 +0800 [thread overview]
Message-ID: <1178828675.4662.4.camel@daplas> (raw)
In-Reply-To: <46434cdea1ce4@wp.pl>
On Thu, 2007-05-10 at 18:48 +0200, Krzysztof Helt wrote:
> Hi,
>
> Below are tests of different scrolling methods for cards I have.
>
> All tested drivers use SCROLL_REDRAW method. I forced SCROLL_MOVE
> method by adding flag FB_READS_FAST.
>
> Here are some conclusions:
> Comparing two new methods: smart blitting and smart blitting with
> merge, the merge of blits gives some speed up at lower bit
> depths, but it is usually lost at higher ones. So we can choose
> both ways (with or without the merge).
>
> The smart blitting is so much faster in many cases comparing to
> the current dump SCROLL_MOVE, that it can replace the current
> method. For some cards it is even faster than SCROLL_REDRAW with
> accelerated fb_imageblit().
>
> The drivers tdfxfb and nvidiafb will benefit from switching to
> SCROLL_MOVE method if the smart blitting is added (the tdfxfb
> even without it). I wonder if Geforce cards also shows this speed
> up if switched to the SCROLL_MOVE method but I have no card to
> test.
>
> The mach64 case is strange: it gives upper hand to smart blitting
> but not at 32-bit depth.
>
> I will prepare a patch with drop-in replacement for current
> SCROLL_MOVE method without blits merging (it is the cleanest
> solution).
Nice benchmarks and results!
The test is done on cards with both accelerated imageblit and copyarea.
Do you get the same results in unaccelerated drivers (vesafb)?
If you do, it might even be wise to change the default from
SCROLL_REDRAW to SCROLL_MOVE...?
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-10 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 16:48 Blitter speed tests (was: smart blitter usage for scrolling) Krzysztof Helt
2007-05-10 20:24 ` Antonino A. Daplas [this message]
2007-05-10 20:36 ` Antonino A. Daplas
2007-05-11 6:00 ` Blitter speed tests (was: smart blitterusage for scr olling) Krzysztof Helt
2007-05-11 12:15 ` Antonino A. Daplas
2007-05-10 20:31 ` Blitter speed tests (was: smart blitter usage for scrolling) Antonino A. Daplas
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=1178828675.4662.4.camel@daplas \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).