From: James Simmons <jsimmons@infradead.org>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK FBDEV] String drawing optimizations.
Date: Thu, 15 May 2003 21:27:38 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0305152104400.6330-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20030513003427.GA19121@vana.vc.cvut.cz>
> What about getting rid of one-char putc, implementing it in terms of
> putcs? I'm doing it in matroxfb patches, and nobody complained yet, and
> with current length of {fbcon,accel}_putc{s,} I was not able to find
> measurable speed difference between putc and putc through putcs variants.
Hm. I compressed all the image drawing functions into accel_putcs which is
used in many places. I then placed accel_putc() into fbcon_putc(). I could
have accel_putcs() called in fbcon_putc(). The advantage is smaller
amount of code. The offset is a big more overhead plus a function call.
What do people think here?
next prev parent reply other threads:[~2003-05-15 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:02 [BK FBDEV] String drawing optimizations James Simmons
2003-05-13 0:34 ` Petr Vandrovec
2003-05-15 20:27 ` James Simmons [this message]
2003-05-16 8:24 ` [Linux-fbdev-devel] " Geert Uytterhoeven
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=Pine.LNX.4.44.0305152104400.6330-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).