From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Saumya Panda <saumya.iisc@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: Problem in EROFS: Not able to read the files after mount
Date: Wed, 22 Jan 2020 12:37:03 +0800 [thread overview]
Message-ID: <20200122043655.GB6542@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CAHmfoRn+YjEwxmZLTeDVN9Oja=7QTi14oEtpD5x7URT_X9dJ5w@mail.gmail.com>
On Wed, Jan 22, 2020 at 09:27:45AM +0530, Saumya Panda wrote:
> Hi Gao,
> Thanks for the info. After I enabled the said configuration, I am now
> able to read the files after mount. But I am seeing Squashfs has better
> compression ratio compared to Erofs (more than 60% than that of Erofs). Am
> I missing something? I used lz4hc while making the Erofs image.
>
> ls -l enwik*
> -rw-r--r-- 1 saumya users 61280256 Jan 21 03:22 enwik8.erofs.img
> -rw-r--r-- 1 saumya users 37355520 Jan 21 03:34 enwik8.sqsh
> -rw-r--r-- 1 saumya users 558133248 Jan 21 03:25 enwik9.erofs.img
> -rw-r--r-- 1 saumya users 331481088 Jan 21 03:35 enwik9.sqsh
Yes, it's working as expect. Currently EROFS is compressed in 4k
fixed-sized output compression granularity as mentioned in many
available materials. That is the use case for our smartphones.
You should compare with similar block configuration of squashfs.
and there are some 3rd data by other folks as well [1].
In the future, we will support other compression algorithms and
larger compressed size (> 4k).
[1] In chinese,
https://blog.csdn.net/scnutiger/article/details/102507596
Thanks,
Gao Xiang
next prev parent reply other threads:[~2020-01-22 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 6:55 Problem in EROFS: Not able to read the files after mount Saumya Panda
2020-01-20 7:41 ` Gao Xiang via Linux-erofs
2020-01-22 3:57 ` Saumya Panda
2020-01-22 4:37 ` Gao Xiang via Linux-erofs [this message]
2020-01-29 4:13 ` Saumya Panda
2020-01-29 4:50 ` Gao Xiang via Linux-erofs
2020-01-29 4:59 ` Gao Xiang via Linux-erofs
2020-03-20 8:00 ` Saumya Panda
2020-03-20 11:16 ` Gao Xiang via Linux-erofs
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=20200122043655.GB6542@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=linux-erofs@lists.ozlabs.org \
--cc=hsiangkao@aol.com \
--cc=saumya.iisc@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).