[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28469095-127d-4d2b-b4b8-d83192d74951@oracle.com>
Date: Fri, 11 Jul 2025 10:16:09 +0100
From: John Garry <john.g.garry@...cle.com>
To: Damien Le Moal <dlemoal@...nel.org>, agk@...hat.com, snitzer@...nel.org,
mpatocka@...hat.com, song@...nel.org, yukuai3@...wei.com, hch@....de,
nilay@...ux.ibm.com, axboe@...nel.dk, cem@...nel.org
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
Subject: Re: [PATCH v6 0/6] block/md/dm: set chunk_sectors from stacked dev
stripe size
On 11/07/2025 09:44, Damien Le Moal wrote:
>> This series now sets chunk_sectors limit to share stripe size.
> Hmm... chunk_sectors for a zoned device is the zone size. So is this all safe
> if we are dealing with a zoned block device that also supports atomic writes ?
> Not that I know of any such device, but better be safe, so maybe for now do not
> enable atomic write support on zoned devices ?
I don't think that we need to do anything specific there.
Patch 1/6 catches if the chunk size is less than the atomic write max size.
Having said that, if a zoned device did support atomic writes then it
would be very odd to have its atomic write max size > zone size anyway.
Thanks,
John
Powered by blists - more mailing lists