Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2448558pxu; Mon, 7 Dec 2020 06:58:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJwgrDDC/YjtPYtjsrDUCaxXDTOLZ+xa0LhtuB2sqjp5OP8ph3zVAbcMIwwl/mFQM33RiE/T X-Received: by 2002:a50:eb44:: with SMTP id z4mr6667226edp.167.1607353137302; Mon, 07 Dec 2020 06:58:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607353137; cv=none; d=google.com; s=arc-20160816; b=P+V7iIlGYE1dk2TP7pvpNNRyTpXUGCfDUw+6Uu9UVzgH0HZaUtwRz9926sGKSnHLz2 hsKWMS/FLX7c/ff2fKI+HKoS80VWDJmP/FQUdXLsGQn1HZw5uYKk8kEt7QfkQj13Uc2N vPYDBcGz7NPHsO8uxflI98xPJ+AU6jKuuRXzpZDJzHX6W9SacsuSkVfMqEgfLyvdjJNh JysftmXE5fA6yVFFPYbcprbl9Y+1p7gGRcKYn2xkJ15A3nVOyram4op0Ot9is4iTPjqZ xW3kG0r3451b91NfXiPoXdJ134YhwWQbWdkOCK51Jt/RA3jqsnfSQAPSWUUFGLfKkQZB O8Iw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=cChp1c47g4NtdWXYmXfnJKZb0fT/NBEKIp1YK4lJf0A=; b=Vf74YLRxOlxS7bxC5ceeOflFegGDZ2BT+PIINbM2jXJfvvi2qc9whi5QfRkcgLG8f2 PFMVQrGdr0wjj2YnsL2OOty8ADEdTYoAmZUnHtkOJsOpKmBiPBmxy5JK9HE7vfxd7XDN jMFiXjjbVthtu23EjToid3tz1RnxMJNiroLTOXepWI9wFSfFiIajimlBX7Q5pkmD5pSO ySRkraAWaCWe5uO+jOk64+1FfBgVIbmrxFF9bhqJ9HFZ0qPmeqRqt19DFLFLetf7oO4m 1CwvxTQS84nUAptuSsQ1Y9Yb0Lv+QHyTiq/3Yb8gjxmbC4Nbdbsx2VatdXmeSbxFE1Ii plvw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lv26si6636224ejb.218.2020.12.07.06.58.33; Mon, 07 Dec 2020 06:58:57 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726202AbgLGO47 (ORCPT + 99 others); Mon, 7 Dec 2020 09:56:59 -0500 Received: from mx2.suse.de ([195.135.220.15]:50144 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbgLGO46 (ORCPT ); Mon, 7 Dec 2020 09:56:58 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 7663EAB63; Mon, 7 Dec 2020 14:56:17 +0000 (UTC) Subject: Re: [RFC PATCH v2 0/2] add simple copy support To: Christoph Hellwig , SelvaKumar S Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org, axboe@kernel.dk, damien.lemoal@wdc.com, sagi@grimberg.me, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, dm-devel@redhat.com, snitzer@redhat.com, selvajove@gmail.com, nj.shetty@samsung.com, joshi.k@samsung.com, javier.gonz@samsung.com, "Martin K. Petersen" , Bart Van Assche , Mikulas Patocka , linux-scsi@vger.kernel.org References: <20201204094659.12732-1-selvakuma.s1@samsung.com> <20201207141123.GC31159@lst.de> From: Hannes Reinecke Message-ID: <01fe46ac-16a5-d4db-f23d-07a03d3935f3@suse.de> Date: Mon, 7 Dec 2020 15:56:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20201207141123.GC31159@lst.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/7/20 3:11 PM, Christoph Hellwig wrote: > So, I'm really worried about: > > a) a good use case. GC in f2fs or btrfs seem like good use cases, as > does accelating dm-kcopyd. I agree with Damien that lifting dm-kcopyd > to common code would also be really nice. I'm not 100% sure it should > be a requirement, but it sure would be nice to have > I don't think just adding an ioctl is enough of a use case for complex > kernel infrastructure. > b) We had a bunch of different attempts at SCSI XCOPY support form IIRC > Martin, Bart and Mikulas. I think we need to pull them into this > discussion, and make sure whatever we do covers the SCSI needs. > And we shouldn't forget that the main issue which killed all previous implementations was a missing QoS guarantee. It's nice to have simply copy, but if the implementation is _slower_ than doing it by hand from the OS there is very little point in even attempting to do so. I can't see any provisions for that in the TPAR, leading me to the assumption that NVMe simple copy will suffer from the same issue. So if we can't address this I guess this attempt will fail, too. Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer