From: Michal Marek <mmarek@suse.cz>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Kbuild: use normal compression settings for tar*-pkg
Date: Thu, 27 Sep 2012 17:06:24 +0200 [thread overview]
Message-ID: <50646B70.5010100@suse.cz> (raw)
In-Reply-To: <20120911004633.GA21147@localhost>
On 11.9.2012 02:46, Fengguang Wu wrote:
> On Sat, Sep 08, 2012 at 12:47:59PM -0700, Andi Kleen wrote:
>> From: Andi Kleen <ak@linux.intel.com>
>>
>> For large kernel configurations (like a distribution kernel)
>> targz-pkg takes a quite long time to just do the compression.
>> I clocked it at 15+mins for a SUSE kernel like config on a fast
>> system. And tarxz and bzip2 are even slower.
>>
>> The main reason is that the script that is doing the taring sets
>> the highest compression level (-9). When I change it to just
>> use the defaults the gzip time for the same kernel goes down
>> to ~3 mins. I haven't tested xz and bzip, but I expect those
>> to be much faster too.
>>
>> I'm not willing to wait that long for a small compression
>> gain. So just change the script to use the defaults.
>
> Makes sense to me.
>
> Reviewed-by: Fengguang Wu <fengguang.wu@intel.com>
Applied to kbuild.git#kbuild.
Michal
next prev parent reply other threads:[~2012-09-27 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 19:47 [PATCH] Kbuild: use normal compression settings for tar*-pkg Andi Kleen
2012-09-11 0:46 ` Fengguang Wu
2012-09-11 3:01 ` Andi Kleen
2012-09-11 4:21 ` Fengguang Wu
2012-09-27 15:06 ` Michal Marek [this message]
2012-09-12 16:01 ` Zdenek Kaspar
2012-09-12 16:16 ` Andi Kleen
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=50646B70.5010100@suse.cz \
--to=mmarek@suse.cz \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.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 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.