From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56A8CC4332F for ; Thu, 4 Nov 2021 17:36:11 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0721D611C9 for ; Thu, 4 Nov 2021 17:36:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 0721D611C9 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4HlW5P523qz2yQ3 for ; Fri, 5 Nov 2021 04:36:09 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=lst.de (client-ip=213.95.11.211; helo=verein.lst.de; envelope-from=hch@lst.de; receiver=) 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 lists.ozlabs.org (Postfix) with ESMTPS id 4HlW5L1z3Xz2xvv for ; Fri, 5 Nov 2021 04:36:04 +1100 (AEDT) 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" 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> 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) X-BeenThere: linux-erofs@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development of Linux EROFS file system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: nvdimm@lists.linux.dev, Mike Snitzer , linux-s390@vger.kernel.org, linux-erofs@lists.ozlabs.org, Eric Sandeen , virtualization@lists.linux-foundation.org, linux-xfs@vger.kernel.org, dm-devel@redhat.com, linux-fsdevel@vger.kernel.org, Dan Williams , linux-ext4@vger.kernel.org, Ira Weiny , Christoph Hellwig Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" 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.