From: Baoquan He <bhe@redhat.com>
To: Lasse Collin <lasse.collin@tukaani.org>
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
Date: Thu, 18 Feb 2016 08:48:17 +0800 [thread overview]
Message-ID: <20160218004817.GA2704@x1.redhat.com> (raw)
In-Reply-To: <20160217195755.02b9f970@tukaani.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
next prev parent reply other threads:[~2016-02-18 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 15:34 About support XZ-compressed kernel on x86 Baoquan He
2016-02-12 15:41 ` Baoquan He
2016-02-13 18:57 ` Lasse Collin
2016-02-14 13:31 ` Baoquan He
2016-02-15 20:26 ` Lasse Collin
2016-02-16 13:20 ` Baoquan He
2016-02-17 17:57 ` Lasse Collin
2016-02-18 0:48 ` Baoquan He [this message]
2016-02-19 20:19 ` Lasse Collin
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=20160218004817.GA2704@x1.redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alain@knaff.lu \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=vgoyal@redhat.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 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).