public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] zram: add zstd to the supported algorithms list
Date: Thu, 24 Aug 2017 13:30:38 +0900	[thread overview]
Message-ID: <20170824043038.GA13922@bgram> (raw)
In-Reply-To: <20170824014936.4738-1-sergey.senozhatsky@gmail.com>

Hello Sergey,

On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote:
> Add ZSTD to the list of supported compression algorithms.
> 
> Official benchmarks [1]:

First of all, thanks for the work!

I want to ask one thing.

Could you add some benchmark(e.g.,) result(comp ratio and speed)
compared to (inflate, lzo, lz4)?

I want to see how much it's good for small data that ours is 4K.
Thanks!

> 
> Compressor name         Ratio   Compression     Decompress.
> zstd 1.1.3 -1           2.877   430 MB/s        1110 MB/s
> zlib 1.2.8 -1           2.743   110 MB/s        400 MB/s
> brotli 0.5.2 -0         2.708   400 MB/s        430 MB/s
> quicklz 1.5.0 -1        2.238   550 MB/s        710 MB/s
> lzo1x 2.09 -1           2.108   650 MB/s        830 MB/s
> lz4 1.7.5               2.101   720 MB/s        3600 MB/s
> snappy 1.1.3            2.091   500 MB/s        1650 MB/s
> lzf 3.6 -1              2.077   400 MB/s        860 MB/s
> 
> [1] https://github.com/facebook/zstd
> 
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> ---
>  drivers/block/zram/zcomp.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/block/zram/zcomp.c b/drivers/block/zram/zcomp.c
> index 5b8992beffec..cc66daec7bbc 100644
> --- a/drivers/block/zram/zcomp.c
> +++ b/drivers/block/zram/zcomp.c
> @@ -31,6 +31,9 @@ static const char * const backends[] = {
>  #endif
>  #if IS_ENABLED(CONFIG_CRYPTO_842)
>  	"842",
> +#endif
> +#if IS_ENABLED(CONFIG_CRYPTO_ZSTD)
> +	"zstd",
>  #endif
>  	NULL
>  };
> -- 
> 2.14.1
> 

  reply	other threads:[~2017-08-24  4:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  1:49 [PATCH] zram: add zstd to the supported algorithms list Sergey Senozhatsky
2017-08-24  4:30 ` Minchan Kim [this message]
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
     [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=20170824043038.GA13922@bgram \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.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