All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yue Hu <huyue2@yulong.com>
To: linux-erofs@lists.ozlabs.org
Cc: huyue2@yulong.com, geshifei@yulong.com, zhangwen@yulong.com,
	shaojunjun@yulong.com
Subject: [RFC PATCH 0/2] erofs-utils: compression inline feature
Date: Mon, 25 Oct 2021 20:30:42 +0800	[thread overview]
Message-ID: <cover.1635162978.git.huyue2@yulong.com> (raw)

Now, we only support tail-end inline data for uncompressed file. We should
also support it for compressed file to decrease tail extent I/O and save
save more space. That is original intention from Xiang.

Note that, current mapping logic code in erofsuse is only based on
non-bigpcluster in erofsfuse, but i would like to present it. May refine
it for big pcluster later. Let's foucs on this on-disk improvement first.

Thanks.


Yue Hu (2):
  erofs-utils: support tail-packing inline compressed data
  erofs-utils: fuse: support tail-packing inline compressed data

 include/erofs/internal.h |  2 +
 include/erofs_fs.h       |  6 ++-
 lib/compress.c           | 74 ++++++++++++++++++++++++-------
 lib/compressor.c         |  9 ++--
 lib/decompress.c         |  4 ++
 lib/inode.c              | 50 +++++++++++----------
 lib/zmap.c               | 95 +++++++++++++++++++++++++++++++++++++---
 mkfs/main.c              |  6 +++
 8 files changed, 199 insertions(+), 47 deletions(-)

-- 
2.29.0




             reply	other threads:[~2021-10-25 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 12:30 Yue Hu [this message]
2021-10-25 12:30 ` [RFC PATCH 1/2] erofs-utils: support tail-packing inline compressed data Yue Hu
2021-10-26 12:00   ` Gao Xiang
2021-10-27  1:58     ` Yue Hu
2021-10-27  7:21       ` Yue Hu
2021-10-27  7:34         ` Gao Xiang
2021-10-27  8:02           ` Yue Hu
2021-10-25 12:30 ` [RFC PATCH 2/2] erofs-utils: fuse: " 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.1635162978.git.huyue2@yulong.com \
    --to=huyue2@yulong.com \
    --cc=geshifei@yulong.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=shaojunjun@yulong.com \
    --cc=zhangwen@yulong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.