All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Video subsystem draft
Date: Sun, 27 Nov 2005 04:09:04 +0200	[thread overview]
Message-ID: <43891540.6010103@nic.fi> (raw)
In-Reply-To: <200511262052.53100.okuji@enbug.org>

Yoshinori K. Okuji wrote:
> On Saturday 26 November 2005 01:28 am, Vesa Jääskeläinen wrote:
>>> Compression might make the performance horrible, because PPF is very
>>> optimized.
>> When there is a caching implemented in a one day, it's only initial
>> cost. So far I haven't seen performance problems with this. But then
>> again I haven't tried it too much.
> 
> I must test it myself, too. The performance of reading a compressed file is 
> slow, because of seeking. Seeking forward is fast, but seeking backward is 
> very slow. So compression makes sense for OS images, but not much for font 
> files.

> The most important part is the initial cost, BTW. Since a boot loader must be 
> quick to start up (otherwise, the user loses some seconds every time), 
> caching is not so important.

There is this transparent gzip support in gz file open, that diagnoses
file to decide wether it is gzipped or not. If there is transparent
option specified, it can also read nongzipped files. This would allow
user to pack font file if there is a need to compress it (of course with
cost of speed)

If I remember correctly I also saw caching of sectors in disk code, so
basicly if disk cache is big enough old font data will already be in
memory. And this will only cause little delay as there is no I/O
latency. Actual testing in real hardware will tell how good this is. I
am currently only running this on vmware.




  reply	other threads:[~2005-11-27  2:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 11:24 Video subsystem draft Vesa Jääskeläinen
2005-10-23 15:03 ` Timothy Baldwin
2005-10-23 15:24   ` Vesa Jääskeläinen
2005-10-28  3:21 ` Yoshinori K. Okuji
2005-10-28 13:59   ` Vesa Jääskeläinen
2005-11-17 23:19     ` Vesa Jääskeläinen
2005-11-18 11:06       ` Yoshinori K. Okuji
2005-11-22 19:06         ` Vesa Jääskeläinen
2005-11-25 20:25           ` Yoshinori K. Okuji
2005-11-26  0:28             ` Vesa Jääskeläinen
2005-11-26 14:36               ` Vincent Pelletier
2005-11-26 19:54                 ` Yoshinori K. Okuji
2005-11-27  1:48                 ` Vesa Jääskeläinen
2005-12-09 22:44                   ` Marco Gerards
2005-12-10  0:19                     ` Yoshinori K. Okuji
2005-12-10 10:31                     ` Vesa Jääskeläinen
2005-12-10 21:01                       ` Marco Gerards
2005-12-10 21:23                         ` Vesa Jääskeläinen
2005-12-10 20:48                     ` Vesa Jääskeläinen
2005-12-10 21:15                       ` Marco Gerards
2005-12-10 22:14                         ` Vesa Jääskeläinen
2005-12-10 22:32                           ` Marco Gerards
2005-12-10 23:11                             ` Vesa Jääskeläinen
2005-11-27  2:00                 ` Vesa Jääskeläinen
2005-11-26 19:52               ` Yoshinori K. Okuji
2005-11-27  2:09                 ` Vesa Jääskeläinen [this message]
2005-12-09 22:33                   ` Marco Gerards
2005-11-28 21:29               ` Vesa Jääskeläinen
2005-12-06 15:18                 ` Vesa Jääskeläinen

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=43891540.6010103@nic.fi \
    --to=chaac@nic.fi \
    --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.