From: Tor Vic <torvic9@mailbox.org>
To: Jann Horn <jannh@google.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-efi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] x86: Add CONFIG_KERNEL_UNCOMPRESSED support
Date: Wed, 22 Jan 2025 15:52:23 +0100 [thread overview]
Message-ID: <a6d347be-efdf-4cd8-b43a-5179a58b6e72@mailbox.org> (raw)
In-Reply-To: <CAG48ez3ddjXA0HiRyS-wT6Fs_fkX-5cf9XRD061YhJu+NZ8dGw@mail.gmail.com>
On 1/22/25 15:30, Jann Horn wrote:
>>
>> Hello,
>>
>> In my opinion 'lz4 -9' doesn't make much sense.
>> It's terribly slow and the compression ratio is also not exactly good.
>>
>> Instead, zstd seems to be a much better choice. Not quite as ultra fast
>> as lz4 levels 1 to 3, but much better compression.
>
> I think you're describing a slightly different usecase.
>
> My goal here is something I can use for when I build a kernel, boot it
> in QEMU, test something, and then immediately throw the kernel away -
> I don't care that much how much disk space the kernel image uses, and
> the goal I'm optimizing for is pretty much just the time needed for
> one build followed by one boot.
Ah, yes, fair enough. In that case, 'lz4 -1' makes the most sense I
guess. Sorry for the noise.
Tor
next prev parent reply other threads:[~2025-01-22 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 22:16 Jann Horn
2025-01-22 13:30 ` Ard Biesheuvel
2025-01-22 13:54 ` Jann Horn
2025-01-22 14:19 ` Tor Vic
2025-01-22 14:30 ` Jann Horn
2025-01-22 14:52 ` Tor Vic [this message]
2025-01-22 14:21 ` Ard Biesheuvel
2025-02-23 18:33 ` Ingo Molnar
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=a6d347be-efdf-4cd8-b43a-5179a58b6e72@mailbox.org \
--to=torvic9@mailbox.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®