From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] split floppy support off biosdisk
Date: Wed, 18 Jun 2008 03:36:55 -0400 [thread overview]
Message-ID: <1213774615.21026.18.camel@rd> (raw)
In-Reply-To: <ca0f59980806172355r7baa70cbk606c91d4810b4302@mail.gmail.com>
On Wed, 2008-06-18 at 14:55 +0800, Bean wrote:
> You can try Robert's case:
>
> grub-mkimage -d . -o core.img pc ext2 lvm raid
50764 image
35090 image.lzo
27308 image.gz
27012 image.bz2
24470 image.lzma
> The uncompressed part need to be added as well, which is 1280 byte.
It's actually going to depend on the decompression algorithm.
> My concern about other compression is that even if space problem can
> be fixed now, but the limit is not far away, so we may have to worry
> about it again when new code is added, lzma could be a way to solve
> this once and for all.
We would save 7782 bytes going to gzip or 10620 bytes going to lzma.
There is not much difference as long as we abandon lzop in favor of
something else.
If I run string on the image to be compressed, I see all function names,
such as grub_biosdisk_get_diskinfo_int13_extensions. I don't see why we
need function names there. Function names starting with "grub_" take
4590 bytes. It looks like we have some reserves for slimming down the
core.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-18 7:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 17:48 [RFC] split floppy support off biosdisk Robert Millan
2008-06-16 0:32 ` Pavel Roskin
2008-06-16 6:30 ` Bean
2008-06-16 9:15 ` Robert Millan
2008-06-16 11:03 ` Bean
2008-06-16 11:20 ` Javier Martín
2008-06-16 11:47 ` Bean
2008-06-16 12:09 ` Javier Martín
2008-06-16 12:37 ` Bean
2008-06-16 21:31 ` Robert Millan
2008-06-17 2:03 ` Bean
2008-06-17 2:47 ` Javier Martín
2008-06-17 3:06 ` Bean
2008-06-17 14:39 ` Javier Martín
2008-06-17 14:52 ` Bean
2008-06-17 17:23 ` Javier Martín
2008-06-17 17:35 ` Bean
2008-06-18 3:14 ` Javier Martín
2008-06-18 3:49 ` Pavel Roskin
2008-06-18 6:55 ` Bean
2008-06-18 7:36 ` Pavel Roskin [this message]
2008-06-18 8:01 ` Bean
2008-06-18 11:29 ` Bean
2008-06-18 17:37 ` Robert Millan
2008-06-18 11:40 ` Javier Martín
2008-06-18 13:12 ` Bean
2008-06-18 13:28 ` Bean
2008-06-18 13:33 ` Javier Martín
2008-06-18 17:32 ` Isaac Dupree
2008-06-18 17:38 ` Robert Millan
2008-06-18 3:48 ` Javier Martín
2008-06-17 15:02 ` Bean
2008-06-17 15:54 ` Pavel Roskin
2008-06-18 17:53 ` Yoshinori K. Okuji
2008-06-17 12:22 ` Robert Millan
2008-06-17 12:33 ` Robert Millan
2008-06-17 12:54 ` Robert Millan
2008-06-18 17:52 ` Yoshinori K. Okuji
2008-06-18 22:15 ` Robert Millan
2008-06-18 23:56 ` Pavel Roskin
2008-06-19 2:14 ` Yoshinori K. Okuji
2008-06-19 2:37 ` Pavel Roskin
2008-06-19 12:20 ` Robert Millan
2008-06-19 19:22 ` Pavel Roskin
2008-06-16 13:06 ` Pavel Roskin
2008-06-16 14:06 ` Bean
2008-06-16 14:38 ` Pavel Roskin
2008-06-16 21:13 ` Robert Millan
2008-06-16 21:12 ` Robert Millan
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=1213774615.21026.18.camel@rd \
--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.