Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: wIA1KIacVeS4Hvqog9ySjbZa/cZctLWFdoYxhoaX6Tij8PqMsjrMU4IjFZJPVVMeeE4B8yw74m
 wxRH/ZWn7lhgLqRidhBwSAJ1HXg05q7/g5dFWQZ4QXSOSOauLDflQAXepKQ/6SbeZb1NEJu/oq
 yIx8arVS31WhCF6ItXZzzDDHKwdm0V2PXneRJF8jpSjWEJ3Sy1bj4vybuyFzLVwEF79CSxQ3FZ
 /nW+he5zOkd1A9M/qDefJT4zl7WTddQS/wK9lC3Y/7HliWdz0UyqzDbXE9DW7dnxH7IWtpCvKT
 UzE=
From:   Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To:     =?iso-8859-1?Q?Javier_Gonz=E1lez?= <javier@javigon.com>,
        Max Gurtovoy <mgurtovoy@nvidia.com>
CC:     SelvaKumar S <selvakuma.s1@samsung.com>,
        "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
        "axboe@kernel.dk" <axboe@kernel.dk>,
        Damien Le Moal <Damien.LeMoal@wdc.com>,
        "kch@kernel.org" <kch@kernel.org>,
        "sagi@grimberg.me" <sagi@grimberg.me>,
        "snitzer@redhat.com" <snitzer@redhat.com>,
        "selvajove@gmail.com" <selvajove@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "nj.shetty@samsung.com" <nj.shetty@samsung.com>,
        "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
        "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        "dm-devel@redhat.com" <dm-devel@redhat.com>,
        "joshi.k@samsung.com" <joshi.k@samsung.com>,
        "kbusch@kernel.org" <kbusch@kernel.org>,
        "joshiiitr@gmail.com" <joshiiitr@gmail.com>,
        "hch@lst.de" <hch@lst.de>
Subject: Re: [RFC PATCH v5 0/4] add simple copy support
Thread-Topic: [RFC PATCH v5 0/4] add simple copy support
Thread-Index: AQHXByxPYjd3lKFugEyHev6iOAHEsg==
Date:   Tue, 13 Apr 2021 18:36:21 +0000
Message-ID: <BYAPR04MB4965A79071C8DC9DA9D49FC8864F9@BYAPR04MB4965.namprd04.prod.outlook.com>
References: <BYAPR04MB49652982D00724001AE758C986729@BYAPR04MB4965.namprd04.prod.outlook.com>
 <5BE5E1D9-675F-4122-A845-B0A29BB74447@javigon.com>
 <c7848f1c-c2c1-6955-bf20-f413a44f9969@nvidia.com>
 <20210411192641.ya6ntxannk3gjyl5@mpHalley.localdomain>
 <3a52cc06-27ce-96a4-b180-60fc269719ba@nvidia.com>
 <20210413182558.v2lynge6aleazgbv@mpHalley.localdomain>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 07d44658-af8d-42c8-1008-08d8feab094c
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2021 18:36:21.9379
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: aQk3lW+pLtNEJaw5UIPu+n5AFE/A8oQRNwDjAjm6oHMAyu0LP9WmDOsb68NccbHEFTRPO9hMVwBDlSjMkOBsdMPgv/Qe81f99GpO9FE2oXM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR04MB5831
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 4/13/21 11:26, Javier Gonz=E1lez wrote:=0A=
>>> I believe there is space for extensions to simple copy. But given the=
=0A=
>>> experience with XCOPY, I can imagine that changes will be incremental,=
=0A=
>>> based on very specific use cases.=0A=
>>>=0A=
>>> I think getting support upstream and bringing deployed cases is a very=
=0A=
>>> good start.=0A=
>> Copying data (files) within the controller/subsystem from ns_A to ns_B =
=0A=
>> using NVMf will reduce network BW and memory BW in the host server.=0A=
>>=0A=
>> This feature is well known and the use case is well known.=0A=
> Definitely.=0A=
>=0A=
=0A=
I've a working code for nvmet for simple copy, I'm waiting to resolve=0A=
the host interface for REQ_OP_COPY so I can post it with this series.=0A=
=0A=
Let me know if someone wants to collaborate offline on that.=0A=
=0A=
IMHO we first need to sort out the host side interface which is=0A=
a challenge for years and it is not that easy to get it right=0A=
based on the history.=0A=
=0A=
=0A=