Linux-EROFS Archive on lore.kernel.org
 help / color / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Gao Xiang <gaoxiang25@huawei.com>, Chao Yu <chao@kernel.org>,
	<linux-erofs@lists.ozlabs.org>
Cc: Gao Xiang <xiang@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] erofs: drop all vle annotations for runtime names
Date: Thu, 21 Nov 2019 09:12:41 +0800
Message-ID: <c12e9c9d-74ed-2beb-4e07-f9fdd731d00f@huawei.com> (raw)
In-Reply-To: <20191108033733.63919-1-gaoxiang25@huawei.com>

On 2019/11/8 11:37, Gao Xiang wrote:
> VLE was an old informal name of fixed-sized output
> compression came from released ATC'19 paper [1].
> 
> Drop those old annotations since erofs can handle
> all encoded clusters in block-aligned basis, which
> is wider than fixed-sized output compression after
> larger clustersize feature is fully implemented.
> 
> Unaligned encoded data won't be considered in EROFS
> since it's not friendly to inplace I/O and decompression
> inplace.
> 
> a) Fixed-sized output compression with 16KB pcluster:
>   ___________________________________
>  |xxxxxxxx|xxxxxxxx|xxxxxxxx|xxxxxxxx|
>  |___ 0___|___ 1___|___ 2___|___ 3___| physical blocks
> 
> b) Block-aligned fixed-sized input compression with
>    16KB pcluster:
>   ___________________________________
>  |xxxxxxxx|xxxxxxxx|xxxxxxxx|xxx00000|
>  |___ 0___|___ 1___|___ 2___|___ 3___| physical blocks
> 
> c) Block-unaligned fixed-sized input compression with
>    16KB compression unit:
>   ____________________________________________
>  |..xxxxxx|xxxxxxxx|xxxxxxxx|xxxxxxxx|x.......|
>  |___ 0___|___ 1___|___ 2___|___ 3___|___ 4___| physical blocks
> 
> Refine better names for those as well.
> 
> [1] https://www.usenix.org/conference/atc19/presentation/gao
> 
> Cc: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  3:25 [PATCH] " Gao Xiang
2019-11-08  3:37 ` [PATCH v2] " Gao Xiang
2019-11-21  1:12   ` Chao Yu [this message]

Reply instructions:

You may reply publically 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=c12e9c9d-74ed-2beb-4e07-f9fdd731d00f@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=chao@kernel.org \
    --cc=gaoxiang25@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiang@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

Linux-EROFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-erofs/0 linux-erofs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-erofs linux-erofs/ https://lore.kernel.org/linux-erofs \
		linux-erofs@lists.ozlabs.org linux-erofs@ozlabs.org
	public-inbox-index linux-erofs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.ozlabs.lists.linux-erofs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git