linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: linux-erofs@lists.ozlabs.org
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] erofs-utils: release 1.7
Date: Thu, 21 Sep 2023 13:26:25 +0800	[thread overview]
Message-ID: <ZQvUAd8r50cTK+s5@hsiangkao-PC> (raw)

Hi folks,

After almost another 6 months, a new version of erofs-utils 1.7 is
available at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git tags/v1.7

It mainly includes the following changes:
  - support arbitrary valid block sizes in addition to page size;
  - (mkfs.erofs) arrange on-disk meta with Breadth-First Traversal instead;
  - support long xattr name prefixes (Jingbo Xu);
  - support UUID functionality without libuuid (Norbert Lange);
  - (mkfs.erofs, experimental) add DEFLATE algorithm support;
  - (mkfs.erofs, experimental) support building images directly from tarballs;
  - (dump.erofs) print more superblock fields (Guo Xuenan);
  - (mkfs.erofs, experimental) introduce preliminary rebuild mode (Jingbo Xu);
  - various bugfixes and cleanups (Sandeep Dhavale, Guo Xuenan, Yue Hu,
          Weizhao Ouyang, Kelvin Zhang, Noboru Asai, Yifan Zhao and Li Yiyan);

In brief, this version supports tarerofs, DEFLATE algorithm, and new
on-disk features to help the Composefs model.

In the next erofs-utils versions, we are going to improve mkfs
performance by supporting multi-threaded reproducible builds and
optimizing data deduplication & metadata flushing speed.  In addition,
other enhancements like erofsfuse improvements [1], hardware accelerator
and preliminary Zstd algorithm support are on the way too.

Comments, questions are welcome as always, yet time is still needed for
them to be landed (EROFS upstream development is a little part of our
kernel jobs).  It's always worth trying, and any contribution is much
appreciated.

Thanks,
Gao Xiang

[1] https://lore.kernel.org/r/20230918090306.2524624-1-lyy0627@sjtu.edu.cn

                 reply	other threads:[~2023-09-21 17:22 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=ZQvUAd8r50cTK+s5@hsiangkao-PC \
    --to=xiang@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).