From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Minchan Kim <minchan@kernel.org>,
Yuwen Chen <ywen.chen@foxmail.com>,
Richard Chang <richardycc@google.com>,
Brian Geffon <bgeffon@google.com>,
Fengyu Lian <licayy@outlook.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org
Subject: Re: [PATCHv6 0/6] zram: introduce writeback bio batching
Date: Sun, 23 Nov 2025 08:49:17 +0900 [thread overview]
Message-ID: <wdju2lsmlwvz7oqaku5xe6gl22t3pdbgcpgkdcxxeqavwxgc7o@4bmil6a3zsgp> (raw)
In-Reply-To: <20251122135406.dd38efa8bad778bce0daa046@linux-foundation.org>
On (25/11/22 13:54), Andrew Morton wrote:
> On Sat, 22 Nov 2025 16:40:23 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
>
> > As writeback is becoming more and more common the longstanding
> > limitations of zram writeback throughput are becoming more
> > visible. Introduce writeback bio batching so that multiple
> > writeback bio-s can be processed simultaneously.
>
> Thanks, I updated mm.git's mm-unstable branch to this version.
>
> > v5 -> v6:
> > - added some comments to make code clearer
> > - use write lock for batch size limit store (Andrew)
> > - err on 0 batch size (Brian)
> > - pickup reviewed-by tags (Brian)
>
> Here's how this v6 series altered mm-unstable:
Looks right. Thanks!
prev parent reply other threads:[~2025-11-22 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 7:40 Sergey Senozhatsky
2025-11-22 7:40 ` [PATCHv6 1/6] " Sergey Senozhatsky
2025-11-22 7:40 ` [PATCHv6 2/6] zram: add writeback batch size device attr Sergey Senozhatsky
2025-11-24 15:50 ` Brian Geffon
2025-11-22 7:40 ` [PATCHv6 3/6] zram: take write lock in wb limit store handlers Sergey Senozhatsky
2025-11-22 7:40 ` [PATCHv6 4/6] zram: drop wb_limit_lock Sergey Senozhatsky
2025-11-22 7:40 ` [PATCHv6 5/6] zram: rework bdev block allocation Sergey Senozhatsky
2025-11-22 7:40 ` [PATCHv6 6/6] zram: read slot block idx under slot lock Sergey Senozhatsky
2025-11-22 21:54 ` [PATCHv6 0/6] zram: introduce writeback bio batching Andrew Morton
2025-11-22 23:49 ` Sergey Senozhatsky [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=wdju2lsmlwvz7oqaku5xe6gl22t3pdbgcpgkdcxxeqavwxgc7o@4bmil6a3zsgp \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=licayy@outlook.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=ywen.chen@foxmail.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