From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] File readahead buffering
Date: Tue, 22 Jul 2008 17:44:53 -0400 [thread overview]
Message-ID: <1216763094.5601.1.camel@dv> (raw)
In-Reply-To: <20080722120632.7aa611ce@gibibit.com>
On Tue, 2008-07-22 at 12:06 -0700, Colin D Bennett wrote:
> I agree that TGA is not, in general, a great choice for an image format
> (unless it is faster to load a large background image -- a 1024x768 RGB
> PNG file may take more time to decompress than a TGA image would take
> to load -- although perhaps an uncompressed PNG file would be
> comparable in speed to load). However, I have not been able to load any
> PNG images that I have tried to use. Something about the chunk type not
> being supported.
Strange. It's working for me. You may want to post that file to the
list.
> If the buffering is not done in the file I/O layer, then the font
> loading, theme file loading, image file loading, etc. will all need to
> do their own buffering, which IMHO is more error prone and makes those
> modules use more code to handle low level I/O stuff, which detracts
> from their specific purpose.
>
> Also, this is no small increase in speed, but from 10x to 100x increase
> in performance for some cases where small sequential reads are
> performed.
OK, then you may have a case.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-22 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 15:43 [PATCH] File readahead buffering Colin D Bennett
2008-07-22 18:48 ` Pavel Roskin
2008-07-22 19:06 ` Colin D Bennett
2008-07-22 21:44 ` Pavel Roskin [this message]
2008-07-23 4:14 ` Colin D Bennett
2008-07-23 2:05 ` Bean
2008-07-23 2:43 ` Javier Martín
2008-07-23 14:33 ` Colin D Bennett
2008-07-23 14:56 ` Colin D Bennett
2008-07-24 9:51 ` Bean
2008-07-26 17:32 ` Colin D Bennett
2008-07-26 18:14 ` Bean
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=1216763094.5601.1.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.