Linux-Block Archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCHv2 00/17] zram: convert to custom comp API and allow algorithms configuration
Date: Wed, 8 May 2024 16:41:28 +0900	[thread overview]
Message-ID: <20240508074128.GG8623@google.com> (raw)
In-Reply-To: <20240506075834.302472-1-senozhatsky@chromium.org>

On (24/05/06 16:58), Sergey Senozhatsky wrote:
> 	This patch set moves zram from crypto API to a custom compression
> API which allows us to tune and configure compression algorithms,
> something that crypto API, unfortunately, doesn't support. Basically,
> this seroes brings back the bits of comp "backend" code that we had
> many years ago. This means that if we want zram to support new
> compression algorithms we need to implement corresponding backends.
> 
>         Currently, zram supports a pretty decent number of comp backends:
> lzo, lzorle, lz4, lz4hc, 842, deflate, zstd
> 
>         At this point we handle 2 parameters: a compression level and
> a pre-trained compression dictionary. Which seems like a good enough
> start. The list will be extended in the future.
> 
> Examples:
> 
> - changes default compression level
>         echo "algo=zstd level=11" > /sys/block/zram0/comp_algorithm
> 
> - passes path to a pre-trained dictionary
>         echo "algo=zstd dict=/etc/dictionary" > /sys/block/zram0/comp_algorithm

I'll send v3 shortly, which adds pre-trained dictionary support to
lz4 and lz4hc compression backends. Apparently lz4/lz4hc can use
dictionaries pre-trained with zstd --init, just like zstd.

      parent reply	other threads:[~2024-05-08  7:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  7:58 [PATCHv2 00/17] zram: convert to custom comp API and allow algorithms configuration Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 01/17] zram: move from crypto API to custom comp backends API Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 02/17] zram: add lzo and lzorle compression backends support Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 03/17] zram: add lz4 compression backend support Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 04/17] zram: add lz4hc " Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 05/17] zram: add zstd " Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 06/17] zram: pass estimated src size hint to zstd Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 07/17] zram: add zlib compression backend support Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 08/17] zram: add 842 " Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 09/17] zram: check that backends array has at least one backend Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 10/17] zram: introduce zcomp_config structure Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 11/17] zram: extend comp_algorithm attr write handling Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 12/17] zram: support compression level comp config Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 13/17] zram: add support for dict " Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 14/17] zram: add dictionary support to zstd backend Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 15/17] zram: add config init/release backend callbacks Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 16/17] zram: share dictionaries between per-CPU contexts Sergey Senozhatsky
2024-05-06  7:58 ` [PATCHv2 17/17] Documentation/zram: add documentation for algorithm parameters Sergey Senozhatsky
2024-05-08  7:41 ` Sergey Senozhatsky [this message]

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=20240508074128.GG8623@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).