From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161960AbcBRAsY (ORCPT ); Wed, 17 Feb 2016 19:48:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42694 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965354AbcBRAsX (ORCPT ); Wed, 17 Feb 2016 19:48:23 -0500 Date: Thu, 18 Feb 2016 08:48:17 +0800 From: Baoquan He To: Lasse Collin Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, alain@knaff.lu, phillip@lougher.demon.co.uk, akpm@linux-foundation.org, keescook@chromium.org, bp@alien8.de, vgoyal@redhat.com Subject: Re: About support XZ-compressed kernel on x86 Message-ID: <20160218004817.GA2704@x1.redhat.com> References: <20160212153407.GA2731@x1.redhat.com> <20160213205729.49789fee@tukaani.org> <20160214133138.GA2552@x1.redhat.com> <20160215222622.7e159519@tukaani.org> <20160216132020.GA2517@x1.redhat.com> <20160217195755.02b9f970@tukaani.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160217195755.02b9f970@tukaani.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/17/16 at 07:57pm, Lasse Collin wrote: > On 2016-02-16 Baoquan He wrote: > > On 02/15/16 at 10:26pm, Lasse Collin wrote: > > > Yes, like all zeros. I wrote another explanation just in case it > > > helps: > > > > Yes, this is great and very helpful for people who want to understand > > this details. I want to make some change to improve the readability of > > the description in boot/compressed/misc.c, do you mind if I put these > > there? Or you can post a patch to adjust it. > > It's fine for me if you want to do it, although I think the current > description there is quite good already. OK. I still don't understand below snippet taken from misc.c. As you said overwriting happened when the write position quickly approaches the read position. how could it happpen if the input pointer is moving faster than the output pointer? * The output pointer can only overrun the input pointer if the input * pointer is moving faster than the output pointer. A condition only * triggered by data whose compressed form is larger than the * uncompressed * form. Thanks Baoquan > > -- > Lasse Collin | IRC: Larhzu @ IRCnet & Freenode