From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Richard Chang <richardycc@google.com>,
Minchan Kim <minchan@kernel.org>,
Brian Geffon <bgeffon@google.com>,
David Stevens <stevensd@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org
Subject: Re: [PATCHv2 0/7] zram: introduce compressed data writeback
Date: Sun, 18 Jan 2026 18:34:37 -0800 [thread overview]
Message-ID: <20260118183437.6b11e6c43c7701759b73d22c@linux-foundation.org> (raw)
In-Reply-To: <20251201094754.4149975-1-senozhatsky@chromium.org>
On Mon, 1 Dec 2025 18:47:47 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> 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.
I'll move this series and the "zram: use u32 for entry ac_time
tracking" series into mm-stable soon, but the review coverage is thin.
It would be good to get some more reviewer input on these zram/zsmalloc
changes. We haven't heard from Minchan for a couple of months. Is
there someone else who can step up and help out?
Thanks.
prev parent reply other threads:[~2026-01-19 2:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:47 Sergey Senozhatsky
2025-12-01 9:47 ` [PATCHv2 1/7] " Sergey Senozhatsky
2026-01-07 3:50 ` zhangdongdong
2026-01-07 4:28 ` Sergey Senozhatsky
2026-01-07 7:28 ` zhangdongdong
2026-01-07 10:14 ` Sergey Senozhatsky
2026-01-08 2:57 ` zhangdongdong
2026-01-08 3:39 ` Sergey Senozhatsky
2026-01-08 10:36 ` zhangdongdong
2026-01-13 4:54 ` 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
2026-01-19 2:34 ` Andrew Morton [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=20260118183437.6b11e6c43c7701759b73d22c@linux-foundation.org \
--to=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=senozhatsky@chromium.org \
--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