linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kyungsik.lee@lge.com (Kyungsik Lee)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 -next 0/5] Add support for LZ4-compressed kernel
Date: Wed, 6 Mar 2013 15:15:05 +0900	[thread overview]
Message-ID: <20130306061505.GA4979@Corona> (raw)
In-Reply-To: <20130305150616.cb737f9b217b8c82051b2ccb@linux-foundation.org>

On Tue, Mar 05, 2013 at 03:06:16PM -0800, Andrew Morton wrote:
> On Tue,  5 Mar 2013 20:47:31 +0900 Kyungsik Lee <kyungsik.lee@lge.com> wrote:
> 
> > This is the third version. In this version, Some codes are fixed
> > and more description and note are added. I would like to thank David Sterba
> > for his review.
> > 
> > The Last patch[5/5] of the patch set is for making x86 and arm default to
> > LZ4-compressed for testing the LZ4 code in the linux-next.
> > It was requested by Andrew Morton in the patch set v2.
> > 
> > Currently, A preliminary version of LZ4 de/compression tool is supported.
> > However, It is expected that we will have a tool with more features
> > once its format is finished.
> 
> What happened to the changelog?  The earlier version at least had some
> rudimentary benchmarking results, but now we don't even have that. 
> 
> Someone should prepare the information explaining why we added this to
> Linux, and I'd prefer that person be you rather than me!  Certainly it
> should include performance measurements - both speed and space.  Also
> it should capture our thinking regarding all the other decompressors,
> explaining why we view it as acceptable to add yet another one.
Sorry, It will have all the information you mentioned. I can reply to
this thread if you want.

Or I might need another patch(v4). I have one thing to be confirmed
regarding LZ4 format. One of the patch set needs to be fixed
if there is a change. After that I can include the information
in the changelog.

> Please, put yourself in the position of someone reading these commits
> in 2017 wondering "why did they merge this".  We should tell them.

Thanks,
Kyungsik

  reply	other threads:[~2013-03-06  6:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 11:47 [PATCH v3 -next 0/5] Add support for LZ4-compressed kernel Kyungsik Lee
2013-03-05 11:47 ` [PATCH v3 -next 1/5] decompressor: Add LZ4 decompressor module Kyungsik Lee
2013-03-05 11:47 ` [PATCH v3 -next 2/5] lib: Add support for LZ4-compressed kernel Kyungsik Lee
2013-03-05 11:47 ` [PATCH v3 -next 3/5] arm: " Kyungsik Lee
2013-04-30 20:56   ` Andrew Morton
2013-05-03  9:02     ` Kyungsik Lee
2013-03-05 11:47 ` [PATCH v3 -next 4/5] x86: " Kyungsik Lee
2013-03-05 16:13   ` H. Peter Anvin
2013-03-06  6:37     ` Kyungsik Lee
2013-04-25 22:43       ` Andrew Morton
2013-03-05 11:47 ` [PATCH v3 -next 5/5] Kconfig: Make x86 and arm kernels default to the LZ4-compressed Kyungsik Lee
2013-03-05 11:58   ` Borislav Petkov
2013-03-05 12:04   ` Florian Fainelli
2013-03-05 23:08     ` Andrew Morton
2013-03-06  9:57       ` Florian Fainelli
2013-03-06 11:16         ` Borislav Petkov
2013-03-05 16:13   ` H. Peter Anvin
2013-03-05 23:06 ` [PATCH v3 -next 0/5] Add support for LZ4-compressed kernel Andrew Morton
2013-03-06  6:15   ` Kyungsik Lee [this message]
2013-03-08  6:39   ` Kyungsik Lee

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=20130306061505.GA4979@Corona \
    --to=kyungsik.lee@lge.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).