linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Vu Tran <vmtran@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: EROFS to support XZ compressed file
Date: Thu, 21 Nov 2019 08:32:13 +0800	[thread overview]
Message-ID: <20191121003205.GA23848@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CAHfisdKeLY8o=b8aAWhKgf9NndaMjBUmfro_D_jhXaGmXQ_6GA@mail.gmail.com>

Hi Vu,

On Wed, Nov 20, 2019 at 11:52:04AM -0500, Vu Tran wrote:
> Hi,
> 
> In my understanding, the work for having EROFS to support XZ (in both
> kernel and userspace utils) is actively developing.  Is it possible to know
> the timeline for when the feature will be available for end users to try
> out?

Streamed-based XZ decompression is not hard for the kernel part. I've talked
to Chao about this offline, he will work on this. (AFAIK, Currently he's busy
in other stuffs.). It can be tried out when this part is ready.

For mkfs part, The problem of fitblk-like XZ compressor is compression time.
Developping a multi-threaded mkfs is not hard even for fixed-sized output
compression (segment-based compression), hacking LZMA2 compressor is more
preferred. Finally I decided to take some time on this (I'm taking much
time on LZMA format and (its entropy coding) range coder now.)

We also hope other forks could join us as well, either filesystem guys
or compression experts... It will be of great help...

Thanks,
Gao Xiang

> 
> Thank you very much and Best Regards,
> Vu Tran

      reply	other threads:[~2019-11-21  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 16:52 EROFS to support XZ compressed file Vu Tran
2019-11-21  0:32 ` Gao Xiang via Linux-erofs [this message]

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=20191121003205.GA23848@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=hsiangkao@aol.com \
    --cc=vmtran@gmail.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).