From: Jens Axboe <axboe@kernel.dk>
To: agk@redhat.com, snitzer@kernel.org, mpatocka@redhat.com,
song@kernel.org, yukuai3@huawei.com, hch@lst.de,
nilay@linux.ibm.com, cem@kernel.org,
John Garry <john.g.garry@oracle.com>
Cc: dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, linux-block@vger.kernel.org,
ojaswin@linux.ibm.com, martin.petersen@oracle.com,
akpm@linux-foundation.org, linux-xfs@vger.kernel.org,
djwong@kernel.org, dlemoal@kernel.org
Subject: Re: [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size
Date: Thu, 17 Jul 2025 06:01:51 -0600 [thread overview]
Message-ID: <175275371113.371765.7347642796595215334.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250711105258.3135198-1-john.g.garry@oracle.com>
On Fri, 11 Jul 2025 10:52:52 +0000, John Garry wrote:
> This value in io_min is used to configure any atomic write limit for the
> stacked device. The idea is that the atomic write unit max is a
> power-of-2 factor of the stripe size, and the stripe size is available
> in io_min.
>
> Using io_min causes issues, as:
> a. it may be mutated
> b. the check for io_min being set for determining if we are dealing with
> a striped device is hard to get right, as reported in [0].
>
> [...]
Applied, thanks!
[1/6] ilog2: add max_pow_of_two_factor()
commit: 6381061d82141909c382811978ccdd7566698bca
[2/6] block: sanitize chunk_sectors for atomic write limits
commit: 1de67e8e28fc47d71ee06ffa0185da549b378ffb
[3/6] md/raid0: set chunk_sectors limit
commit: 4b8beba60d324d259f5a1d1923aea2c205d17ebc
[4/6] md/raid10: set chunk_sectors limit
commit: 7ef50c4c6a9c36fa3ea6f1681a80c0bf9a797345
[5/6] dm-stripe: limit chunk_sectors to the stripe size
commit: 5fb9d4341b782a80eefa0dc1664d131ac3c8885d
[6/6] block: use chunk_sectors when evaluating stacked atomic write limits
commit: 63d092d1c1b1f773232c67c87debe557aab5aca0
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-07-17 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 10:52 John Garry
2025-07-11 10:52 ` [PATCH v7 1/6] ilog2: add max_pow_of_two_factor() John Garry
2025-07-11 10:52 ` [PATCH v7 2/6] block: sanitize chunk_sectors for atomic write limits John Garry
2025-07-11 10:52 ` [PATCH v7 3/6] md/raid0: set chunk_sectors limit John Garry
2025-07-11 10:52 ` [PATCH v7 4/6] md/raid10: " John Garry
2025-07-11 10:52 ` [PATCH v7 5/6] dm-stripe: limit chunk_sectors to the stripe size John Garry
2025-07-11 10:52 ` [PATCH v7 6/6] block: use chunk_sectors when evaluating stacked atomic write limits John Garry
2025-07-11 11:43 ` [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size Martin K. Petersen
2025-07-17 8:00 ` John Garry
2025-07-17 12:01 ` Jens Axboe [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=175275371113.371765.7347642796595215334.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=ojaswin@linux.ibm.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®