From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.garry@linux.dev>
Cc: axboe@kernel.dk, hch@lst.de, mkp@kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: cap atomic write size by PI buffer size constraints take #2
Date: Tue, 15 Sep 2026 11:01:49 +0200 [thread overview]
Message-ID: <20260915090148.GA15715@lst.de> (raw)
In-Reply-To: <20260914132323.208321-1-john.garry@linux.dev>
On Mon, Sep 14, 2026 at 02:23:23PM +0100, John Garry wrote:
> Commit 1418b5633ca9 ("block: cap atomic write size by PI buffer size
> constraints") attempted to fix atomic writes limits according to integrity
> limits. However, it just reduced the atomic_write_max_sectors. The other
> atomic write limits - unit min and unit max - are not derived directly
> from this value.
>
> Update blk_atomic_writes_update_limits() to properly set the atomic write
> limits according to integrity limits.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-09-15 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:23 [PATCH] block: cap atomic write size by PI buffer size constraints take #2 John Garry
2026-09-15 9:01 ` Christoph Hellwig [this message]
2026-09-15 12:53 ` Jens Axboe
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=20260915090148.GA15715@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=john.garry@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mkp@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