From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Alexey Romanov <avromanov@salutedevices.com>
Cc: minchan@kernel.org, senozhatsky@chromium.org, axboe@kernel.dk,
terrelln@fb.com, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, kernel@salutedevices.com
Subject: Re: [PATCH v1 0/3] zram: introduce crypto-backend api
Date: Wed, 20 Nov 2024 12:15:29 +0900 [thread overview]
Message-ID: <20241120031529.GD2668855@google.com> (raw)
In-Reply-To: <20241119122713.3294173-1-avromanov@salutedevices.com>
On (24/11/19 15:27), Alexey Romanov wrote:
> Since we use custom backend implementation, we remove the ability
> for users to use algorithms from crypto backend. This breaks
> backward compatibility, user doesn't necessarily use one of the
> algorithms from "custom" backends defined in zram folder.
Sorry, no, we are not adding this for a hypothetical scenario.
> For example, he can use some driver with hardware compression support.
Such as? Pretty much all H/W compression modules (I'm aware of)
that people use with zram are out-of-tree.
next prev parent reply other threads:[~2024-11-20 3:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 12:27 [PATCH v1 0/3] zram: introduce crypto-backend api Alexey Romanov
2024-11-19 12:27 ` [PATCH v1 1/3] zram: pass zcomp instead of zcomp_params to create_context method Alexey Romanov
2024-11-19 12:27 ` [PATCH v1 2/3] zram: store crypto backends in list instead of array Alexey Romanov
2024-11-19 12:27 ` [PATCH v1 3/3] zram: introduce crypto-api backend Alexey Romanov
2024-11-19 12:34 ` Christoph Hellwig
2024-11-19 13:04 ` Alexey Romanov
2024-11-19 13:08 ` Christoph Hellwig
2024-11-22 14:59 ` kernel test robot
2024-11-20 3:15 ` Sergey Senozhatsky [this message]
2024-11-21 12:11 ` [PATCH v1 0/3] zram: introduce crypto-backend api Alexey Romanov
2024-11-21 15:53 ` 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=20241120031529.GD2668855@google.com \
--to=senozhatsky@chromium.org \
--cc=avromanov@salutedevices.com \
--cc=axboe@kernel.dk \
--cc=kernel@salutedevices.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=terrelln@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.