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 2134F2C8B for ; Thu, 4 Nov 2021 17:36:02 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id ACAA76732D; Thu, 4 Nov 2021 18:35:59 +0100 (CET) Date: Thu, 4 Nov 2021 18:35:59 +0100 From: Christoph Hellwig To: "Darrick J. Wong" Cc: Christoph Hellwig , Eric Sandeen , Dan Williams , Mike Snitzer , Ira Weiny , dm-devel@redhat.com, linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev, linux-s390@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org, linux-ext4@vger.kernel.org, virtualization@lists.linux-foundation.org Subject: Re: futher decouple DAX from block devices Message-ID: <20211104173559.GB31740@lst.de> References: <20211018044054.1779424-1-hch@lst.de> <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> <20211104081740.GA23111@lst.de> <20211104173417.GJ2237511@magnolia> Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211104173417.GJ2237511@magnolia> User-Agent: Mutt/1.5.17 (2007-11-01) On Thu, Nov 04, 2021 at 10:34:17AM -0700, Darrick J. Wong wrote: > /me wonders, are block devices going away? Will mkfs.xfs have to learn > how to talk to certain chardevs? I guess jffs2 and others already do > that kind of thing... but I suppose I can wait for the real draft to > show up to ramble further. ;) Right now I've mostly been looking into the kernel side. An no, I do not expect /dev/pmem* to go away as you'll still need it for a not DAX aware file system and/or application (such as mkfs initially). But yes, just pointing mkfs to the chardev should be doable with very little work. We can point it to a regular file after all.