From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] split floppy support off biosdisk
Date: Tue, 17 Jun 2008 16:39:03 +0200 [thread overview]
Message-ID: <1213713543.6330.24.camel@localhost> (raw)
In-Reply-To: <ca0f59980806162006ocace82cw47f264945d56bc22@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
El mar, 17-06-2008 a las 11:06 +0800, Bean escribió:
> AFAIK, lzma decompresser don't need intermediate buffers, it operates
> directly on the input and output buffer, for example, the lzmadecoder
> in coreboot:
I think you didn't see the intermediate buffer because it is hidden in
the Probs field passed through the decoderstate struct. I've googled my
way through the net to find what the hell "probs" mean, and I still
don't understand ten contiguous lines of the LZMA code. What I could
find is that
http://qa.coreboot.org/docs/doxygen/lzma_8c-source.html
provides the decoder with about 32KiB of "scratchpad" memory and will
reject decompressing files which "require" (as somehow indicated by the
first 5 bytes of the LZMA stream) more than that. I don't know if that
space is used for dictionaries, trees, forests or a Matrix full of
virtual monkeys hitting keys at random until the decompressed stream is
achieved, but its size seems to impose constraints at the time of
compression (probably a maximum -n level) that merit investigation.
PS: have you tested the performance of other compression algorithms like
gzip-deflate (much simpler) or bzip2 (near LZMA for small files but with
less memory requisites)?
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-06-17 14:38 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 [this message]
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
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=1213713543.6330.24.camel@localhost \
--to=lordhabbit@gmail.com \
--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.