[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175275371113.371765.7347642796595215334.b4-ty@kernel.dk>
Date: Thu, 17 Jul 2025 06:01:51 -0600
From: Jens Axboe <axboe@...nel.dk>
To: agk@...hat.com, snitzer@...nel.org, mpatocka@...hat.com,
song@...nel.org, yukuai3@...wei.com, hch@....de, nilay@...ux.ibm.com,
cem@...nel.org, John Garry <john.g.garry@...cle.com>
Cc: dm-devel@...ts.linux.dev, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, linux-block@...r.kernel.org,
ojaswin@...ux.ibm.com, martin.petersen@...cle.com,
akpm@...ux-foundation.org, linux-xfs@...r.kernel.org, djwong@...nel.org,
dlemoal@...nel.org
Subject: Re: [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev
stripe size
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
Powered by blists - more mailing lists