From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Optimizing bitblit.c / fb_pad_*
Date: Sat, 30 Jul 2005 20:43:42 +0200 [thread overview]
Message-ID: <42EBCA5E.4030209@t-online.de> (raw)
In-Reply-To: <42EB7A10.4080601@gmail.com>
Hi Antonino,
>> + if (fast_8x16)
>> + for (i = 16; i--; ) {
>> + *dstp = src[15-i];
>> + dstp += pitch;
>> + }
>
>
> why not make it to something like this?
>
> for (i = cellsize; i--;) {
> *dstp = src[cellsize-1-i];
> dstp += pitch;
> }
>
> This way, it will work with any fontsize, as long as the width
> is a 8-bit size-aligned. You can do the same with
> fb_pad_aligned_buffer(), so the rest can benefit too.
>
fb_pad_unaligned() could be optimized localy, there are other cases of
memcpy(), e.g. in softcursor, etc.
Well, this was nothing but a quick ´n dirty hack, I tried to find out if
there
is still potential for optimizations. If people agree that the gain in speed
justifies it, I will try to look at those parts of the kernel _after_ I have
submitted my cyberblade/i1 driver. I have to admit that I ´m not familar
(enough) with the layers above the hardware driver level right now.
> PS: Next time you submit a patch, add a Signed-off-line.
ack. btw, should a new driver first be presented in
linux-fbdev-devel@lists.sourceforge.net or lkml?
cu,
Knut
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-30 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 9:21 Optimizing bitblit.c / fb_pad_* Knut Petersen
2005-07-30 13:01 ` Antonino A. Daplas
2005-07-30 18:43 ` Knut Petersen [this message]
2005-07-31 0:54 ` Antonino A. Daplas
2005-08-03 17:34 ` 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=42EBCA5E.4030209@t-online.de \
--to=knut_petersen@t-online.de \
--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).