linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: linux-erofs@lists.ozlabs.org
Cc: kernel-team@android.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Miao Xie <miaoxie@huawei.com>
Subject: [ANNOUNCE] erofs-utils: release 1.3
Date: Tue, 1 Jun 2021 00:20:56 +0800	[thread overview]
Message-ID: <20210531162055.GA18956@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)

Hi folks,

A new version erofs-utils 1.3 is available at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git tags/v1.3

It mainly includes the following changes:
   - support new big pcluster feature together with Linux 5.13+;
   - optimize buffer allocation logic (Hu Weiwen);
   - optimize build performance for large directories (Hu Weiwen);
   - add support to override uid / gid (Hu Weiwen);
   - add support to adjust lz4 history window size (Huang Jianan);
   - add a manual for erofsfuse;
   - add support to limit max decompressed extent size;
   - various bugfixes and cleanups;

One notable update is that it now supports EROFS big pcluster [1][2],
which allows compressing variable-sized data into more than 1 fs block
by using fixed-sized output compression [3]. It can be used for some
(sub)-files with specific data access patterns (such as oneshot data
segments which need better compression ratio and thus better sequential
performance.)

Note that users can write their own per-(sub)files big pcluster
strategies to adjust pclustersize in time according to file type static
analysis or historical tracing data in z_erofs_get_max_pclusterblks().
And default strategies will be developed and built-in laterly in the
future.

btw, I've heard more in-market products shipped with EROFS, for example
OPPO [4] and Coolpad [5] with some public news plus more in-person
contacts from time to time. It's always worth trying and feedback or
contribution is welcomed.

[1] https://www.kernel.org/doc/html/latest/filesystems/erofs.html
[2] https://lore.kernel.org/r/20210407043927.10623-1-xiang@kernel.org 
[3] https://www.usenix.org/system/files/atc19-gao.pdf
[4] https://new.qq.com/omn/20210312/20210312A0D9HT00.html
[5] https://hunchmag.com/helio-g80-erofs-48-mp-arcsoft-and-cool-os-coolpad-cool-2-smartphone-announced/

Thanks,
Gao Xiang

                 reply	other threads:[~2021-05-31 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210531162055.GA18956@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=xiang@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.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).