From: Gao Xiang <hsiangkao@redhat.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v6] f2fs: compress: support compress level
Date: Fri, 4 Dec 2020 11:21:40 +0800 [thread overview]
Message-ID: <20201204032140.GD1963435@xiangao.remote.csb> (raw)
In-Reply-To: <15afffcc-636d-b678-0c01-b2fad98d9311@huawei.com>
On Fri, Dec 04, 2020 at 11:11:03AM +0800, Chao Yu wrote:
> On 2020/12/4 10:47, Gao Xiang wrote:
...
>
> > future (and add more dependency to algorithms, you might see BWT-based bzip2
> > removal patch
>
> Oops, is that really allowed? I don't this is a good idea...and I don't see there
> are deletions from fs/ due to similar reason...
Fortunately, bzip is quite slow algorithm, so not affective at all.
My personal opinion based on compress algorithm principle (just for reference
as well...)
- zlib should be better replaced with libdeflate if possible, the main point
is that many hardware accelerator for deflate (LZ77 + huffman) are
available;
- lzo is not attractive from its format complexity and its CR/performance
goal so lz4 is generally better due to its format design;
- lzo-rle, oops, just introduced for zram I think, not sure quite helpful
for file data (since anonymous pages are generally RLE-effective due to
many repeative data.) But it'd be good if lzo author accepts it.
Thanks,
Gao Xiang
>
> Thanks,
> >
>
next prev parent reply other threads:[~2020-12-04 3:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 6:17 [PATCH v6] f2fs: compress: support compress level Chao Yu
2020-12-03 19:32 ` [f2fs-dev] " Eric Biggers
2020-12-04 0:31 ` Gao Xiang
2020-12-04 1:56 ` Chao Yu
2020-12-04 2:06 ` Gao Xiang
2020-12-04 2:38 ` Chao Yu
2020-12-04 2:47 ` Gao Xiang
2020-12-04 3:11 ` Chao Yu
2020-12-04 3:21 ` Gao Xiang [this message]
2020-12-04 7:09 ` Chao Yu
2020-12-04 7:43 ` Gao Xiang
2020-12-04 8:50 ` Chao Yu
2020-12-04 9:10 ` Gao Xiang
2020-12-04 1:18 ` Chao Yu
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=20201204032140.GD1963435@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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