[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4q45sjEih8vIC-V@kernel.org>
Date: Fri, 17 Jan 2025 15:09:10 -0500
From: Mike Snitzer <snitzer@...nel.org>
To: John Garry <john.g.garry@...cle.com>, axboe@...nel.dk,
mpatocka@...hat.com
Cc: axboe@...nel.dk, agk@...hat.com, hch@....de, song@...nel.org,
yukuai3@...wei.com, kbusch@...nel.org, sagi@...mberg.me,
James.Bottomley@...senpartnership.com, martin.petersen@...cle.com,
linux-block@...r.kernel.org, dm-devel@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH RFC v2 0/8] device mapper atomic write support
On Thu, Jan 16, 2025 at 05:02:53PM +0000, John Garry wrote:
> This series introduces initial device mapper atomic write support.
>
> Since we already support stacking atomic writes limits, it's quite
> straightforward to support.
>
> Personalities dm-linear, dm-stripe, and dm-raid1 are supported here, and
> more personalities could be supported in future.
>
> This is still an RFC as I would like to test further.
>
> Based on 3d9a9e9a77c5 (block/for-6.14/block) block: limit disk max
> sectors to (LLONG_MAX >> 9)
>
> Changes to v1:
> - Generic block layer atomic writes enable flag and dm-table rework
> - Add dm-stripe and dm-raid1 support
> - Add bio_trim() patch
This all looks good.
Mikulas, we need Jens to pick up patches 1 and 2. I wouldn't be
opposed to him taking the entire set but I did notice the DM core
(ioctl) version and the 3 DM targets that have had atomic support
added need their version numbers bumped. Given that, likely best for
you (Mikulas) to pick up patches 3-8 after rebasing on Jens' latest
for-6.14/block branch (once Jens picks up patches 1 and 2).
Jens, you cool with picking up patches 1+2 for 6.14? Or too late and
we circle back to this for 6.15?
Either way, for the series:
Reviewed-by: Mike Snitzer <snitzer@...nel.org>
Powered by blists - more mailing lists