From: Richard Weinberger <richard@nod.at>
To: Yufen Yu <yuyufen@huawei.com>
Cc: dedekind1@gmail.com, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [RFC PATCH] ubifs: Add zstd support
Date: Fri, 12 Jan 2018 11:45:49 +0100 [thread overview]
Message-ID: <7790203.HFZG64yrZx@blindfold> (raw)
In-Reply-To: <20180112092421.22095-1-yuyufen@huawei.com>
Yufen Yu,
Am Freitag, 12. Januar 2018, 10:24:21 CET schrieb Yufen Yu:
> Add zstd compression and decompression support to ubifs. zstd at its
> fastest level compresses almost as well as zlib, while offering much
> faster compression and decompression, approaching lzo speeds.
>
> This patch is based on the patch:
> https://patchwork.kernel.org/patch/9892631/
>
> zstd source repository: https://github.com/facebook/zstd
Do you have numbers on how much we gain for UBIFS on a typical embedded
device?
Thanks,
//richard
next prev parent reply other threads:[~2018-01-12 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 9:24 [RFC PATCH] ubifs: Add zstd support Yufen Yu
2018-01-12 10:45 ` Richard Weinberger [this message]
2018-01-16 6:16 ` yuyufen
2018-01-16 10:55 ` Richard Weinberger
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=7790203.HFZG64yrZx@blindfold \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=yuyufen@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