From: Nick Terrell <terrelln@fb.com>
To: Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yann Collet <cyan@fb.com>
Subject: Re: [PATCH] zram: add zstd to the supported algorithms list
Date: Fri, 25 Aug 2017 18:55:44 +0000 [thread overview]
Message-ID: <D01CD6BA-C12D-46AB-8AC1-F03A114FC055@fb.com> (raw)
In-Reply-To: <20170825045036.GA26819@blaptop>
On 8/24/17, 9:51 PM, "Minchan Kim" <minchan@kernel.org> wrote:
>Off-topic:
>
>In all ways, zstd beats deflate. Nick, Right?
Yeah. Since all LZ compression algorithms are heuristics, there are some
rare cases where zlib beats zstd in compression ratio by a bit, but never
speed. In all cases where we've deployed zstd, we've seen aggregate
compression ratio improvements over zlib, and expect the same here.
>With zstd, I doubt we should show "deflate" to user. Many options just
>make user confused.
>The inflate have been there for representing high comp ratio but slower
>speed. However, zstd is better unconditionally compared to deflate
>so how about replacing deflate with zstd?
>
>Sergey, what do you think about it?
next prev parent reply other threads:[~2017-08-25 18:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 1:49 Sergey Senozhatsky
2017-08-24 4:30 ` Minchan Kim
2017-08-24 14:04 ` Sergey Senozhatsky
2017-08-25 4:50 ` Minchan Kim
2017-08-25 5:06 ` Sergey Senozhatsky
2017-08-25 5:27 ` Sergey Senozhatsky
2017-08-25 5:36 ` Minchan Kim
2017-08-25 7:45 ` Sergey Senozhatsky
2017-08-25 8:08 ` Adam Borowski
2017-08-25 18:55 ` Nick Terrell [this message]
[not found] <<20170824014936.4738-1-sergey.senozhatsky@gmail.com>
2017-08-24 21:33 ` Nick Terrell
2017-08-25 0:49 ` Joonsoo Kim
2017-08-25 1:35 ` Nick Terrell
2017-08-25 1:53 ` Sergey Senozhatsky
2017-08-25 2:09 ` Nick Terrell
2017-08-25 2:21 ` Sergey Senozhatsky
2017-08-25 2:46 ` Nick Terrell
2017-08-25 5:26 ` Sergey Senozhatsky
2017-08-25 2:02 ` Joonsoo Kim
2017-08-25 5:19 ` Minchan Kim
2017-08-25 19:31 ` Nick Terrell
2017-08-28 6:52 ` Minchan Kim
2017-08-25 0:51 ` Sergey Senozhatsky
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=D01CD6BA-C12D-46AB-8AC1-F03A114FC055@fb.com \
--to=terrelln@fb.com \
--cc=akpm@linux-foundation.org \
--cc=cyan@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@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
all inboxes | Powered by JetHome®