public inbox for linux-kernel@vger.kernel.org
 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.8
Date: Fri, 9 Aug 2024 08:28:24 +0800	[thread overview]
Message-ID: <ZrViqMFpC6uVEoXK@debian> (raw)

Hi folks,

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

It mainly includes the following changes:

   - (mkfs.erofs) support multi-threaded compression (Yifan Zhao);
   - support Intel IAA hardware accelerator with Intel QPL;
   - add preliminary Zstandard support;
   - (erofsfuse) use FUSE low-level APIs and support multi-threading (Li Yiyan);
   - (mkfs.erofs) support tar source without data (Mike Baynton);
   - (mkfs.erofs) support incremental builds (incomplete, EXPERIMENTAL);
   - (mkfs.erofs) other build performance improvements;
   - (erofsfuse) support building erofsfuse as a static library (ComixHe);
   - various bugfixes and cleanups (Sandeep Dhavale, Noboru Asai,
           Luke T. Shumaker, Yifan Zhao, Hongzhen Luo and Tianyi Liu).

It has been long time since the last release, mainly due to several new
major features and limited incremental builds.  However, it'd be better
not to hold it off any longer, as users have asked for multi-threaded
mkfs support.

In the future erofs-utils versions, we are going to improve incremental
builds, support multi-threaded mkfs for fragments and compressed data
deduplication, multi-threaded fsck/extraction as well as more remote
storage (e.g. HTTP, S3 and OCI registries), stabilize liberofs APIs for
3rd-party applications and eventually find a way to integrate a Rust
version [1].  Also see [2].

Feedback and contribution, as always, are welcomed.

[1] https://github.com/ToolmanP/erofs-rs
[2] https://erofs.docs.kernel.org/en/latest/roadmap.html

Thanks,
Gao Xiang

                 reply	other threads:[~2024-08-09  0:28 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=ZrViqMFpC6uVEoXK@debian \
    --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