From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: Yue Hu <huyue2@yulong.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 5/5] erofs: add on-disk compressed tail-packing inline support
Date: Thu, 30 Dec 2021 12:01:36 +0800 [thread overview]
Message-ID: <331dda35-b5cc-86c9-83ff-b30b383531b6@kernel.org> (raw)
In-Reply-To: <20211228054604.114518-6-hsiangkao@linux.alibaba.com>
On 2021/12/28 13:46, Gao Xiang wrote:
> From: Yue Hu <huyue2@yulong.com>
>
> Introduces erofs compressed tail-packing inline support.
>
> This approach adds a new field called `h_idata_size' in the
> per-file compression header to indicate the encoded size of
> each tail-packing pcluster.
>
> At runtime, it will find the start logical offset of the tail
> pcluster when initializing per-inode zmap and record such
> extent (headlcn, idataoff) information to the in-memory inode.
> Therefore, follow-on requests can directly recognize if one
> pcluster is a tail-packing inline pcluster or not.
>
> Signed-off-by: Yue Hu <huyue2@yulong.com>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2021-12-30 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 5:45 [PATCH v4 0/5] erofs: support tail-packing inline compressed data Gao Xiang
2021-12-28 5:46 ` [PATCH v4 1/5] erofs: tidy up z_erofs_lz4_decompress Gao Xiang
2021-12-28 5:46 ` [PATCH v4 2/5] erofs: introduce z_erofs_fixup_insize Gao Xiang
2021-12-28 5:46 ` [PATCH v4 3/5] erofs: support unaligned data decompression Gao Xiang
2021-12-30 3:14 ` Chao Yu
2021-12-28 5:46 ` [PATCH v4 4/5] erofs: support inline " Gao Xiang
2021-12-28 23:29 ` [PATCH v5 " Gao Xiang
2021-12-30 3:29 ` Chao Yu
2021-12-28 5:46 ` [PATCH v4 5/5] erofs: add on-disk compressed tail-packing inline support Gao Xiang
2021-12-30 4:01 ` Chao Yu [this message]
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=331dda35-b5cc-86c9-83ff-b30b383531b6@kernel.org \
--to=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@yulong.com \
--cc=linux-erofs@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox