From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Richard Chang <richardycc@google.com>,
Minchan Kim <minchan@kernel.org>
Cc: Brian Geffon <bgeffon@google.com>,
David Stevens <stevensd@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: [PATCHv2 0/7] zram: introduce compressed data writeback
Date: Mon, 1 Dec 2025 18:47:47 +0900 [thread overview]
Message-ID: <20251201094754.4149975-1-senozhatsky@chromium.org> (raw)
As writeback becomes more common there is another shortcoming
that needs to be addressed - compressed data writeback. Currently
zram does uncompressed data writeback which is not optimal due to
potential CPU and battery wastage. This series changes suboptimal
uncompressed writeback to a more optimal compressed data writeback.
v1 -> v2:
- made compressed writeback configurable via device attribute
- added missing batch_size documentation
- switched to guard() for init_lock
- more code tweaks and cleanups
Richard Chang (2):
zram: introduce compressed data writeback
zram: introduce writeback_compressed device attribute
Sergey Senozhatsky (5):
zram: document writeback_batch_size
zram: move bd_stat to writeback section
zram: rename zram_free_page()
zram: switch to guard() for init_lock
zram: consolidate device-attr declarations
Documentation/ABI/testing/sysfs-block-zram | 14 +
Documentation/admin-guide/blockdev/zram.rst | 24 +-
drivers/block/zram/zram_drv.c | 589 ++++++++++++--------
drivers/block/zram/zram_drv.h | 1 +
4 files changed, 406 insertions(+), 222 deletions(-)
--
2.52.0.487.g5c8c507ade-goog
next reply other threads:[~2025-12-01 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:47 Sergey Senozhatsky [this message]
2025-12-01 9:47 ` [PATCHv2 1/7] " Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 2/7] zram: introduce writeback_compressed device attribute Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 3/7] zram: document writeback_batch_size Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 4/7] zram: move bd_stat to writeback section Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 5/7] zram: rename zram_free_page() Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 6/7] zram: switch to guard() for init_lock Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 7/7] zram: consolidate device-attr declarations 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=20251201094754.4149975-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-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=richardycc@google.com \
--cc=stevensd@google.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