From: Andi Kleen <ak@linux.intel.com>
To: Nick Terrell <terrelln@fb.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<kernel-team@fb.com>, Chris Mason <clm@fb.com>,
Yann Collet <cyan@fb.com>, Rene Rebe <rene@exactcode.com>,
Adam Borowski <kilobyte@angband.pl>
Subject: Re: [PATCH v2 2/2] x86: Add support for ZSTD-compressed kernel
Date: Tue, 17 Oct 2017 12:45:45 -0700 [thread overview]
Message-ID: <87infdsgly.fsf@linux.intel.com> (raw)
In-Reply-To: <20171012221138.3201900-3-terrelln@fb.com> (Nick Terrell's message of "Thu, 12 Oct 2017 15:11:38 -0700")
Nick Terrell <terrelln@fb.com> writes:
> @@ -133,6 +133,8 @@ $(obj)/vmlinux.bin.lzo: $(vmlinux.bin.all-y) FORCE
> $(call if_changed,lzo)
> $(obj)/vmlinux.bin.lz4: $(vmlinux.bin.all-y) FORCE
> $(call if_changed,lz4)
> +$(obj)/vmlinux.bin.zst: $(vmlinux.bin.all-y) FORCE
> + $(call if_changed,zstd)
In my experience the biggest problem with these options is that the
special command line tools needed for the build are often not installed
on the build systems.
So we turn it off and go back to GZIP to make the kernel build again.
Or we settle on some other option, but then when a better compressor
like ZSTD comes up it's too much trouble to change all the .configs.
There were recently some patches to add a stackprotector automatic
selection that probes if gcc supports stack overflow support,
and if not falls back automatically.
A similar thing for good compression options would seem better:
have a AUTO config option that uses ZSTD and fall back to GZIP
if it's not available. Then put it into defconfig.
I suspect that would increase your user base quite a bit.
-Andi
prev parent reply other threads:[~2017-10-17 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 22:11 [PATCH v2 0/2] Add support for ZSTD-compressed kernel Nick Terrell
2017-10-12 22:11 ` [PATCH v2 1/2] lib: " Nick Terrell
2017-10-12 22:11 ` [PATCH v2 2/2] x86: " Nick Terrell
2017-10-17 19:45 ` Andi Kleen [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=87infdsgly.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rene@exactcode.com \
--cc=terrelln@fb.com \
--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