linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: RFC: Optimizing putcs()
Date: 07 Aug 2002 08:17:44 +0800	[thread overview]
Message-ID: <1028679284.554.37.camel@daplas> (raw)
In-Reply-To: <Pine.GSO.4.21.0208062204390.5852-100000@vervain.sonytel.be>

On Wed, 2002-08-07 at 04:08, Geert Uytterhoeven wrote:

> 
> Just for reference, did you run this benchmark on 2.4.x as well?
> 
> Gr{oetje,eeting}s,
> 
Sort of. The functions in fbcon-cfb*.c are already very fast, because
fbcon and character drawing are tightly integrated together, and
fbcon_cfb8_putcs() is very, very efficient, processing 4 bits per
iteration, instead of 1.  I'm getting numbers like this:

real    0m2.098s
user    0m0.000s
sys     0m2.070s

which was faster(!) than my hardware implementation of putcs, and 5x
faster than 2.5.  Since I'm using an i810 with Video in System RAM,
direct framebuffer access does not carry much overhead.  I just have to
beat fbcon-cfb8, so I thought of placing text data in offscreen graphics
memory to take full advantage of hardware blitting.

At high bit depths (32 bpp), 2.5 with an offscreen buffer is as fast as
2.4.

Tony    




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-08-07  0:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 22:04 RFC: Optimizing putcs() Antonino Daplas
2002-08-06 20:08 ` Geert Uytterhoeven
2002-08-07  0:17   ` Antonino Daplas [this message]
2002-08-07  5:25 ` Antonino Daplas
     [not found] <20020806054957.44715.qmail@web13004.mail.yahoo.com>
2002-08-06 18:11 ` Antonino Daplas
2002-08-08 18:31   ` James Simmons

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=1028679284.554.37.camel@daplas \
    --to=adaplas@pol.net \
    --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).