From: Pavel Roskin <proski@gnu.org>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Christian Ruppert <christian.ruppert@abilis.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Noam Camus <noamc@ezchip.com>
Subject: Re: Uncompressed kernel doesn't build on x86_64
Date: Thu, 14 Nov 2013 18:38:42 -0500 [thread overview]
Message-ID: <20131114183842.2c4b10aa@IRBT4585> (raw)
In-Reply-To: <5284DA98.1060402@gmail.com>
On Thu, 14 Nov 2013 09:13:44 -0500
Austin S Hemmelgarn <ahferroin7@gmail.com> wrote:
> On 2013-11-14 03:32, Christian Ruppert wrote:
> > 2. A patch to enable uncompressed x86 kernels. As stated above, I
> > don't think this makes a lot of sense in itself but it might serve
> > as an example for people working on other platforms with
> > self-extracting kernels and the nozip not-decompression algorithm
> > might be useful on those platforms as well. I only had a single
> > x86-64 machine available to test this, however, so some more
> > testing might be required.
>
> I disagree with the argument that an uncompressed x86 kernel doesn't
> make sense, If you have a very fast boot device, then it is fully
> conceivable that an uncompressed kernel could boot faster than a
> compressed one. I have seen a very large number of systems where the
> LZO compression boots at least twice as fast as gzip or bz2 (because
> the disks are fast enough that a few megabytes of size difference
> make much less of an impact than a slow decompressor).
I concur, the uncompressed kernel certainly makes sense in some cases.
If the kernel runs in an emulator, decompression could be slow.
If the kernel runs in a virtual machine, the kernel would need to be
decompressed separately for every virtual machine. Reading from the
disk would be done only once if several virtual machines are started in
a short period of time.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2013-11-14 23:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 16:34 Uncompressed kernel doesn't build on x86_64 Pavel Roskin
2013-11-13 16:49 ` H. Peter Anvin
2013-11-14 8:32 ` Christian Ruppert
2013-11-14 8:38 ` [PATCH 1/2] init/Kconfig: add option to disable kernel compression Christian Ruppert
2013-11-14 10:21 ` Vineet Gupta
2013-11-15 16:57 ` Christian Ruppert
2013-11-16 9:41 ` Vineet Gupta
2013-11-14 8:38 ` [PATCH 2/2] x86: Add support for uncompressed kernel images Christian Ruppert
2013-11-14 17:31 ` H. Peter Anvin
2013-11-15 9:31 ` Christian Ruppert
2013-11-14 17:45 ` H. Peter Anvin
2013-11-15 9:49 ` Christian Ruppert
2013-11-15 10:06 ` H. Peter Anvin
2013-11-14 14:13 ` Uncompressed kernel doesn't build on x86_64 Austin S Hemmelgarn
2013-11-14 23:38 ` Pavel Roskin [this message]
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=20131114183842.2c4b10aa@IRBT4585 \
--to=proski@gnu.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.ruppert@abilis.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamc@ezchip.com \
/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.