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 0B0EC2080C6; Tue, 10 Dec 2024 10:58:33 +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=1733828316; cv=none; b=NBsQtVd0bOeWcmy6Rgqar4sO9DrnQKuoC9OXhz71N3teorLORsRPP7di3QqrcLyaJoJdn/vRxA83FU3eE2JVhm6cJk5rPVPPwm7/uhpiRkqPdDRJJdFxOw0JkRsFGOSYzUiNFqLmAwO4JDZBL6gbi5PI1tjlDXCEruIU8kQa+AQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1733828316; c=relaxed/simple; bh=d9G4uh5kXI0bl5+4qhmaObA8jCmdOFmW5rrC+dcx+lM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=KmsAC1MFui3Jp5tY9twB7Rx4qfyOw/lVSwS4eDSgEqesvd7+VF6Fn8CM7r6w31HqNk5KSJHSmAW//HO8iO+dmOQ2v+5Ro7p/jKd1XeANrhontM3uLUSkXQBUXsnCM6cHu0XixQ6YKGTruG8wLxAkiKAX7z9DAB7qof/3ZCa0P3A= 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 B1E4368CFE; Tue, 10 Dec 2024 11:58:22 +0100 (CET) Date: Tue, 10 Dec 2024 11:58:22 +0100 From: hch To: Johannes Thumshirn Cc: hch , "Martin K. Petersen" , Nitesh Shetty , Bart Van Assche , Javier Gonzalez , Matthew Wilcox , Keith Busch , 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: <20241210105822.GA3123@lst.de> References: <9d61a62f-6d95-4588-bcd8-de4433a9c1bb@acm.org> <8ef1ec5b-4b39-46db-a4ed-abf88cbba2cd@acm.org> <20241205080342.7gccjmyqydt2hb7z@ubuntu> <20241210071253.GA19956@lst.de> <2a272dbe-a90a-4531-b6a2-ee7c4c536233@wdc.com> Precedence: bulk X-Mailing-List: linux-block@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2a272dbe-a90a-4531-b6a2-ee7c4c536233@wdc.com> User-Agent: Mutt/1.5.17 (2007-11-01) On Tue, Dec 10, 2024 at 08:05:31AM +0000, Johannes Thumshirn wrote: > > Generally agreeing with all you said, but do we actually have any > > serious use case for cross-LU copies? They just seem incredibly > > complex any not all that useful. > > One use case I can think of is (again) btrfs balance (GC, convert, etc) > on a multi drive filesystem. BUT this use case is something that can > just use the fallback read-write path as it is doing now. Who uses multi-device file systems on multiple LUs of the same SCSI target ơr multiple namespaces on the same nvme subsystem?