From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: linux-erofs@lists.ozlabs.org
Cc: nl6720 <nl6720@gmail.com>,
Lasse Collin <lasse.collin@tukaani.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] erofs: add fiemap support with iomap
Date: Fri, 13 Aug 2021 13:29:29 +0800 [thread overview]
Message-ID: <20210813052931.203280-1-hsiangkao@linux.alibaba.com> (raw)
Hi folks,
This patchset mainly addresses fiemap support for EROFS. After this
patchset, end users can observe (un)compressed extent distribution
by hand.
The first patch is also useful for later LZMA support in order to
decompress full LZMA extents if needed (according to specific
strategy.)
Btw, the current development status for LZMA is in the following
branches (yet these are not aimed for the next merge window since
it's still some work to do):
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git/log/?h=erofs/lzma
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/log/?h=experimental-lzma
Thanks,
Gao Xiang
Gao Xiang (2):
erofs: add support for the full decompressed length
erofs: add fiemap support with iomap
fs/erofs/data.c | 15 ++++-
fs/erofs/inode.c | 1 +
fs/erofs/internal.h | 10 ++++
fs/erofs/namei.c | 1 +
fs/erofs/zmap.c | 131 +++++++++++++++++++++++++++++++++++++++++---
5 files changed, 149 insertions(+), 9 deletions(-)
--
2.24.4
next reply other threads:[~2021-08-13 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 5:29 Gao Xiang [this message]
2021-08-13 5:29 ` [PATCH 1/2] erofs: add support for the full decompressed length Gao Xiang
2021-08-14 15:27 ` [PATCH v1.1 " Gao Xiang
2021-08-18 14:11 ` Chao Yu
2021-08-18 15:22 ` [PATCH v1.2] " Gao Xiang
2021-08-16 15:38 ` [PATCH 1/2] " Chao Yu
2021-08-17 0:54 ` [PATCH 1/2] erofs: add support for the full decompressed lengthy Gao Xiang
2021-08-13 5:29 ` [PATCH 2/2] erofs: add fiemap support with iomap Gao Xiang
2021-08-18 14:11 ` Chao Yu
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=20210813052931.203280-1-hsiangkao@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nl6720@gmail.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).