From: Yue Hu <zbestahu@gmail.com>
To: xiang@kernel.org, chao@kernel.org
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
zhangwen@coolpad.com, shaojunjun@coolpad.com, zbestahu@gmail.com,
Yue Hu <huyue2@coolpad.com>
Subject: [RFC PATCH v4 0/2] erofs: support compressed fragments data
Date: Tue, 13 Sep 2022 19:05:50 +0800 [thread overview]
Message-ID: <cover.1663065625.git.huyue2@coolpad.com> (raw)
From: Yue Hu <huyue2@coolpad.com>
This feature can merge tail of per-file or the whole files into a
special inode to achieve greater compression ratio.
Meanwhile, also add a interlaced uncompressed data layout support for
compressed files since fragments feature (and later) can use it.
mkfs v8: https://lore.kernel.org/all/cover.1663065968.git.huyue2@coolpad.com/
changes from v3:
- improve the interlaced layout for non 4K uncompressed data as well (Xiang)
- support 64bit fragment offset for fragment inode and legacy compress (Xiang)
changes from v2:
- enhance the condition to check if pcluster is interlaced or not;
- no typo.
changes from v1:
- fix a compiling error without CONFIG_EROFS_FS_ZIP, reported by kernel test
robot <lkp@intel.com>;
- introduce the term 'interlaced' for patch 1/2 suggested by Xiang;
- fix packed inode failure path when read super pointed out by Xiang;
- use kmap_local_page instead of kmap_atomic pointed out by Xiang;
- use a simpler way to avoid call read fragment data twice suggested by Xiang;
- update commit message change.
Yue Hu (2):
erofs: support interlaced uncompressed data for compressed files
erofs: support on-disk compressed fragments data
fs/erofs/decompressor.c | 47 ++++++++++++++++++-------------
fs/erofs/erofs_fs.h | 31 +++++++++++++++++----
fs/erofs/internal.h | 17 +++++++++--
fs/erofs/super.c | 15 ++++++++++
fs/erofs/sysfs.c | 2 ++
fs/erofs/zdata.c | 48 ++++++++++++++++++++++++++++++-
fs/erofs/zmap.c | 62 +++++++++++++++++++++++++++++++++++++----
7 files changed, 187 insertions(+), 35 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-13 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 11:05 Yue Hu [this message]
[not found] ` <cover.1663066966.git.huyue2@coolpad.com>
2022-09-13 11:05 ` [RFC PATCH v4 1/2] erofs: support interlaced uncompressed data for compressed files Yue Hu
2022-09-16 9:04 ` Gao Xiang
2022-09-13 11:05 ` [RFC PATCH v4 2/2] erofs: support on-disk compressed fragments data Yue Hu
2022-09-16 9:08 ` Gao Xiang
2022-09-17 3:56 ` Yue Hu
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=cover.1663065625.git.huyue2@coolpad.com \
--to=zbestahu@gmail.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaojunjun@coolpad.com \
--cc=xiang@kernel.org \
--cc=zhangwen@coolpad.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