From: "Laszlo Ersek" <lersek@redhat.com>
To: "Schaefer, Daniel" <daniel.schaefer@hpe.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>
Subject: Re: [edk2-devel] Multithreaded compression with LZMA2
Date: Fri, 4 Dec 2020 00:35:00 +0100 [thread overview]
Message-ID: <16c68ee6-19a7-1446-719d-3553a2df842e@redhat.com> (raw)
In-Reply-To: <DF4PR8401MB04449394D5540D7E922BED40E0F20@DF4PR8401MB0444.NAMPRD84.PROD.OUTLOOK.COM>
On 12/03/20 13:11, Schaefer, Daniel wrote:
>
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Thursday, December 3, 2020 18:24
> To: devel@edk2.groups.io <devel@edk2.groups.io>; Schaefer, Daniel <daniel.schaefer@hpe.com>
> Cc: Lin, Derek (HPS SW) <derek.lin2@hpe.com>
> Subject: Re: [edk2-devel] Multithreaded compression with LZMA2
>
> "xz -T" works by splitting the input into blocks, and it generates a
> multi-block compressed output.
>
> Yes, that's correct.
>
>> I'm unsure if the current LZMA
> decompressor that runs inside the firmware (= guided section extractor)
> copes with multi-block input.
>
> I think you're right that it doesn't. But we can make the guided section extractor use that same algorithm(LZMA2) and assign it a different GUID, right?
I guess so...
Thanks
Laszlo
next prev parent reply other threads:[~2020-12-03 23:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 2:59 Multithreaded compression with LZMA2 Daniel Schaefer
2020-12-02 3:36 ` [edk2-devel] " Andrew Fish
2020-12-02 5:21 ` 回复: " gaoliming
2020-12-02 8:24 ` Daniel Schaefer
2020-12-03 10:24 ` Laszlo Ersek
2020-12-03 12:11 ` Daniel Schaefer
2020-12-03 15:57 ` Bret Barkelew
2020-12-04 8:19 ` Daniel Schaefer
2020-12-03 23:35 ` Laszlo Ersek [this message]
2020-12-04 2:28 ` 回复: " gaoliming
2020-12-04 9:02 ` Daniel Schaefer
2020-12-08 6:01 ` 回复: " gaoliming
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-list 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=16c68ee6-19a7-1446-719d-3553a2df842e@redhat.com \
--to=devel@edk2.groups.io \
/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