From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8BA6A3232; Thu, 28 Nov 2024 16:40:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732812022; cv=none; b=CEtQGXeI2/EBaN4tcl36qYDZ04DQdSNVPc2HQ3UTmsIZGHKj9BeAsROICBq9Y8btoma8T9gpuAg2E+pgiClMZxnXUbAuFpUE2B1tpawNIELlhR3TSlT+ZSY9JNMHU+13c6qpIyWgYJrvT2LpMhieMui9MRUOa96S7lARw+GGpgg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732812022; c=relaxed/simple; bh=2KNWJz+dCprzlzJ06B46V4J0MqyaE43k6Qpg1qYPkJg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=mGCOuDT7RR4fodx/myS7G9e2p8U8SO1toZ+ACs5+1qjZpjz8DNET7W9+Q5aYrRH5gBfArxzalyEbznu2vNtLBbTce9EuqkqJh0f1gh9PmUfMrv56yJKYOM1A+0sIslMElAdyJrvpXOBkqIx2LIS6eJSl4uOWaqz7W3O/Qwb5CgE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 7A7A568D96; Thu, 28 Nov 2024 17:40:04 +0100 (CET) Date: Thu, 28 Nov 2024 17:40:02 +0100 From: Christoph Hellwig To: Keith Busch Cc: "Martin K. Petersen" , Bart Van Assche , Nitesh Shetty , Javier Gonzalez , Matthew Wilcox , Christoph Hellwig , Keith Busch , "linux-block@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "linux-scsi@vger.kernel.org" , "io-uring@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "joshi.k@samsung.com" Subject: Re: [PATCHv10 0/9] write hints with nvme fdp, scsi streams Message-ID: <20241128164002.GA26959@lst.de> References: <2b5a365a-215a-48de-acb1-b846a4f24680@acm.org> <20241111093154.zbsp42gfiv2enb5a@ArmHalley.local> <20241112135233.2iwgwe443rnuivyb@ubuntu> <9d61a62f-6d95-4588-bcd8-de4433a9c1bb@acm.org> <8ef1ec5b-4b39-46db-a4ed-abf88cbba2cd@acm.org> Precedence: bulk X-Mailing-List: io-uring@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Thu, Nov 28, 2024 at 08:21:16AM -0700, Keith Busch wrote: > I think of copy a little differently. When you do a normal write > command, the host provides the controller a vector of sources and > lengths. A copy command is like a write command, but the sources are > just logical block addresses instead of memory addresses. > > Whatever solution happens, it would be a real shame if it doesn't allow > vectored LBAs. The token based source bio doesn't seem to extend to > that. POPULATE TOKEN as defined by SCSI/SBC takes a list of LBA ranges as well.