From: Yuwen Chen <ywen.chen@foxmail.com>
To: bgeffon@google.com
Cc: akpm@linux-foundation.org, licayy@outlook.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, minchan@google.com, minchan@kernel.org,
richardycc@google.com, senozhatsky@chromium.org,
ywen.chen@foxmail.com
Subject: Re: [PATCHv3 1/4] zram: introduce writeback bio batching support
Date: Tue, 18 Nov 2025 11:48:07 +0800 [thread overview]
Message-ID: <tencent_3E9743D12F77CFF8B8EBDDB9529EDA975306@qq.com> (raw)
In-Reply-To: <CADyq12zxzi+t727B5sm5z-z3SmRQyMDOmr_tTG1GaMVh6VTWbw@mail.gmail.com>
On Mon, 17 Nov 2025 10:19:22 -0500, Brian Geffon wrote:
> Out of curiosity, why are we doing 1 page per bio? Why are we not
> adding BIO_MAX_VECS before submitting? And then, why are we not
> chaining? Do the block layer maintainers have thoughts?
Mainly because the zram backend device is quite special. When
performing the writeback operation, the probability of continuous
writing is relatively low. If BIO_MAX_VECS is used, it will make
the logic extremely complex. Thank you very much!
next prev parent reply other threads:[~2025-11-18 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 2:34 [PATCHv3 0/4] zram: introduce writeback bio batching Sergey Senozhatsky
2025-11-15 2:34 ` [PATCHv3 1/4] zram: introduce writeback bio batching support Sergey Senozhatsky
2025-11-17 15:19 ` Brian Geffon
2025-11-18 2:08 ` Yuwen Chen
2025-11-18 2:14 ` Sergey Senozhatsky
2025-11-18 3:18 ` Yuwen Chen
2025-11-18 3:36 ` Yuwen Chen
2025-11-18 3:47 ` Sergey Senozhatsky
2025-11-18 3:48 ` Yuwen Chen [this message]
2025-11-18 7:00 ` Sergey Senozhatsky
2025-11-15 2:34 ` [PATCHv3 2/4] zram: add writeback batch size device attr Sergey Senozhatsky
2025-11-15 2:34 ` [PATCHv3 3/4] zram: take write lock in wb limit store handlers Sergey Senozhatsky
2025-11-15 2:34 ` [PATCHv3 4/4] zram: drop wb_limit_lock 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=tencent_3E9743D12F77CFF8B8EBDDB9529EDA975306@qq.com \
--to=ywen.chen@foxmail.com \
--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@google.com \
--cc=minchan@kernel.org \
--cc=richardycc@google.com \
--cc=senozhatsky@chromium.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