From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
Brian Geffon <bgeffon@google.com>,
linux-block@vger.kernel.org, linux-mm@kvack.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: [PATCH v2 0/6] zram: recompression cleanups and tweaks
Date: Wed, 11 Mar 2026 17:42:43 +0900 [thread overview]
Message-ID: <20260311084312.1766036-1-senozhatsky@chromium.org> (raw)
This series is a somewhat random mix of fixups,
recompression cleanups and improvements partly based
on internal conversations. A few patches in the series
remove unexpected or confusing behaviour, e.g. auto
correction of bad priority= param for recompression,
which should have always been just an error. Then it
also removes "chain recompression" which has a tricky,
unexpected and confusing behaviour at times. We also
unify and harden the handling of algo/priority params.
There is also an addition of missing device lock in
algorithm_params_store() which previously permitted
modification of algo params while the device is active.
Sergey Senozhatsky (6):
zram: do not permit params change after init
zram: do not autocorrect bad recompression parameters
zram: drop ->num_active_comps
zram: update recompression documentation
zram: remove chained recompression
zram: unify and harden algo/priority params handling
Documentation/admin-guide/blockdev/zram.rst | 49 ++---
drivers/block/zram/zram_drv.c | 214 ++++++++++----------
drivers/block/zram/zram_drv.h | 1 -
3 files changed, 123 insertions(+), 141 deletions(-)
--
2.53.0.473.g4a7958ca14-goog
next reply other threads:[~2026-03-11 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 8:42 Sergey Senozhatsky [this message]
2026-03-11 8:42 ` [PATCH v2 1/6] zram: do not permit params change after init Sergey Senozhatsky
2026-03-11 8:42 ` [PATCH v2 2/6] zram: do not autocorrect bad recompression parameters Sergey Senozhatsky
2026-03-11 8:42 ` [PATCH v2 3/6] zram: drop ->num_active_comps Sergey Senozhatsky
2026-03-11 8:42 ` [PATCH v2 4/6] zram: update recompression documentation Sergey Senozhatsky
2026-03-11 8:42 ` [PATCH v2 5/6] zram: remove chained recompression Sergey Senozhatsky
2026-03-11 8:42 ` [PATCH v2 6/6] zram: unify and harden algo/priority params handling 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=20260311084312.1766036-1-senozhatsky@chromium.org \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.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