[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220428074926.GG9558@test-zns>
Date: Thu, 28 Apr 2022 13:19:26 +0530
From: Nitesh Shetty <nj.shetty@...sung.com>
To: Damien Le Moal <damien.lemoal@...nsource.wdc.com>
Cc: linux-block@...r.kernel.org, linux-scsi@...r.kernel.org,
dm-devel@...hat.com, linux-nvme@...ts.infradead.org,
linux-fsdevel@...r.kernel.org, nitheshshetty@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 00/10] Add Copy offload support
On Thu, Apr 28, 2022 at 07:05:32AM +0900, Damien Le Moal wrote:
> On 4/27/22 21:49, Nitesh Shetty wrote:
> > O Wed, Apr 27, 2022 at 11:19:48AM +0900, Damien Le Moal wrote:
> >> On 4/26/22 19:12, Nitesh Shetty wrote:
> >>> The patch series covers the points discussed in November 2021 virtual call
> >>> [LSF/MM/BFP TOPIC] Storage: Copy Offload[0].
> >>> We have covered the Initial agreed requirements in this patchset.
> >>> Patchset borrows Mikulas's token based approach for 2 bdev
> >>> implementation.
> >>>
> >>> Overall series supports –
> >>>
> >>> 1. Driver
> >>> - NVMe Copy command (single NS), including support in nvme-target (for
> >>> block and file backend)
> >>
> >> It would also be nice to have copy offload emulation in null_blk for testing.
> >>
> >
> > We can plan this in next phase of copy support, once this series settles down.
>
> So how can people test your series ? Not a lot of drives out there with
> copy support.
>
Yeah not many drives at present, Qemu can be used to test NVMe copy.
--
Nitesh Shetty
Powered by blists - more mailing lists