linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: "Antonino A.Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Blitter speed tests (was: smart blitterusage for scr olling)
Date: Fri, 11 May 2007 08:00:32 +0200	[thread overview]
Message-ID: <46440680635cb@wp.pl> (raw)
In-Reply-To: <46434cdea1ce4@wp.pl> <1178828675.4662.4.camel@daplas> <1178829389.4662.13.camel@daplas>

Dnia 10-05-2007 o godz. 22:36 Antonino A. Daplas napisa³(a):
> On Fri, 2007-05-11 at 04:24 +0800, Antonino A. Daplas wrote:
> > If you do, it might even be wise to change the default from
> > SCROLL_REDRAW to SCROLL_MOVE...?
> > 
> Come to think of it we'll probably just let the driver choose
the scroll
> method.
> 
> SCROLL_MOVE is faster at lower bit depths because the bitmap
preparation
> for the putcs method slows down SCROLL_REDRAW.  But as the bit
depth
> goes up, the amount of data moved by bmove goes up but at a
higher rate
> than the data moved by putcs. Thus SCROLL_MOVE loses its edge
at 16-32
> bpp. At what point these lines intersect we really don't know as it
> depends on the hardware and the driver's imageblit/copyarea
> implementation.
> 

If you want really complicated solution one can switch
FB_READS_FAST flag depending on the bit depth inside each driver ;-)

I think that a simple solution is to leave everything untouched
except tdfxfb and nvidiafb drivers. These two should add
FB_READS_FAST flag permanently to use  blitter for scrolling.

Take into account that the faster machine may speed up the redraw
operation, because it is faster, while blitting will have the
same speed. 

On the other hand, most cards I have cannot even closely compare
their on-board memory bandwidth to the one on newer cards like
Geforce or Radeon (so blitting should be much faster on the newer
cards). The blitting merge can help these cards (no hardware to
tests).

Regards,
Krzysztof

----------------------------------------------------
Wczoraj chodzi³o o honor. Dzisiaj - o sprawiedliwo¶æ.
Mark Wahlberg i Danny Glover w pe³nym akcji filmie 
"STRZELEC" - w kinach od 11 maja.
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fstrzelec.html&sid=1134



-------------------------------------------------------------------------
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/

  reply	other threads:[~2007-05-11  6:00 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
2007-05-10 20:36   ` Antonino A. Daplas
2007-05-11  6:00     ` Krzysztof Helt [this message]
2007-05-11 12:15       ` Blitter speed tests (was: smart blitterusage for scr olling) 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=46440680635cb@wp.pl \
    --to=krzysztof.h1@wp.pl \
    --cc=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).