From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Resource management.
Date: Tue, 22 Feb 2005 06:53:01 +0800 [thread overview]
Message-ID: <200502220653.01286.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502211908520.14500@pentafluge.infradead.org>
On Tuesday 22 February 2005 03:11, James Simmons wrote:
> Hi!
>
> This is my first run at the resource management code. Comments are
> welcomed :-)
>
Hi James,
Where is this going to? What I see are performance penalties. For each
putcs and cursor, it has to call fb_find_resource() which walks the linked list
looking for a resource using strncmp().
What's the goal here?
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-21 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 19:11 Resource management James Simmons
2005-02-21 22:53 ` Antonino A. Daplas [this message]
2005-02-21 23:25 ` James Simmons
2005-02-22 1:01 ` Jon Smirl
2005-02-22 3:53 ` James Simmons
2005-02-22 4:46 ` [Linux-fbdev-devel] " Dave Airlie
2005-02-22 5:13 ` James Simmons
2005-02-22 5:59 ` [Linux-fbdev-devel] " Jon Smirl
2005-02-22 5:23 ` Jon Smirl
2005-02-22 17:23 ` James Simmons
2005-02-22 18:59 ` [Linux-fbdev-devel] " Alex Deucher
2005-02-22 13:25 ` Antonino A. Daplas
2005-02-22 14:06 ` Antonino A. Daplas
2005-02-24 19:57 ` James Simmons
2005-02-24 23:05 ` Antonino A. Daplas
2005-02-28 20:01 ` Resource management II 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=200502220653.01286.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@www.infradead.org \
--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).