[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZjzFB2CzCh1NKlfw@infradead.org>
Date: Thu, 9 May 2024 05:43:51 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org
Subject: Re: [PATCHv3 00/19] zram: convert to custom compression API and
allow algorithms tuning
On Wed, May 08, 2024 at 04:41:53PM +0900, 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.
[...]
> 21 files changed, 1203 insertions(+), 111 deletions(-)
Why can't it? This is an awful lot of crazy code duplication just
to pass a few parameters.
Powered by blists - more mailing lists