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 33FFD2C8B for ; Thu, 4 Nov 2021 08:27:50 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 9396E68AA6; Thu, 4 Nov 2021 09:17:40 +0100 (CET) Date: Thu, 4 Nov 2021 09:17:40 +0100 From: Christoph Hellwig To: Eric Sandeen Cc: Christoph Hellwig , 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: <20211104081740.GA23111@lst.de> References: <20211018044054.1779424-1-hch@lst.de> <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> 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: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> User-Agent: Mutt/1.5.17 (2007-11-01) On Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote: > Christoph, can I ask what the end game looks like, here? If dax is completely > decoupled from block devices, are there user-visible changes? Yes. > If I want to > run fs-dax on a pmem device - what do I point mkfs at, if not a block device? The rough plan is to use the device dax character devices. I'll hopefully have a draft version in the next days. 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 2AAA0C433EF for ; Thu, 4 Nov 2021 08:17:51 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (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 9360E60F9D for ; Thu, 4 Nov 2021 08:17:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 9360E60F9D 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.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 42A8940508; Thu, 4 Nov 2021 08:17:50 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MkvpuLRah0Ov; Thu, 4 Nov 2021 08:17:49 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [IPv6:2605:bc80:3010:104::8cd3:938]) by smtp4.osuosl.org (Postfix) with ESMTPS id D77A740504; Thu, 4 Nov 2021 08:17:48 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id AE677C0019; Thu, 4 Nov 2021 08:17:48 +0000 (UTC) Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id F32B9C0012 for ; Thu, 4 Nov 2021 08:17:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id E829B60817 for ; Thu, 4 Nov 2021 08:17:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpJ_Rc8Ybu06 for ; Thu, 4 Nov 2021 08:17:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by smtp3.osuosl.org (Postfix) with ESMTPS id C01A760811 for ; Thu, 4 Nov 2021 08:17:45 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 9396E68AA6; Thu, 4 Nov 2021 09:17:40 +0100 (CET) Date: Thu, 4 Nov 2021 09:17:40 +0100 From: Christoph Hellwig To: Eric Sandeen Subject: Re: futher decouple DAX from block devices Message-ID: <20211104081740.GA23111@lst.de> References: <20211018044054.1779424-1-hch@lst.de> <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: nvdimm@lists.linux.dev, Mike Snitzer , linux-s390@vger.kernel.org, linux-erofs@lists.ozlabs.org, 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 X-BeenThere: virtualization@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Linux virtualization List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" On Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote: > Christoph, can I ask what the end game looks like, here? If dax is completely > decoupled from block devices, are there user-visible changes? Yes. > If I want to > run fs-dax on a pmem device - what do I point mkfs at, if not a block device? The rough plan is to use the device dax character devices. I'll hopefully have a draft version in the next days. _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization 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 654B3C433FE for ; Thu, 4 Nov 2021 08:17:52 +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 A0286611C3 for ; Thu, 4 Nov 2021 08:17:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A0286611C3 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 4HlGjB2cBKz2yHJ for ; Thu, 4 Nov 2021 19:17:50 +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 4HlGj65PCRz2xt9 for ; Thu, 4 Nov 2021 19:17:46 +1100 (AEDT) Received: by verein.lst.de (Postfix, from userid 2407) id 9396E68AA6; Thu, 4 Nov 2021 09:17:40 +0100 (CET) Date: Thu, 4 Nov 2021 09:17:40 +0100 From: Christoph Hellwig To: Eric Sandeen Subject: Re: futher decouple DAX from block devices Message-ID: <20211104081740.GA23111@lst.de> References: <20211018044054.1779424-1-hch@lst.de> <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> 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, 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 Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote: > Christoph, can I ask what the end game looks like, here? If dax is completely > decoupled from block devices, are there user-visible changes? Yes. > If I want to > run fs-dax on a pmem device - what do I point mkfs at, if not a block device? The rough plan is to use the device dax character devices. I'll hopefully have a draft version in the next days. 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 AB4C9C433F5 for ; Thu, 4 Nov 2021 08:18:09 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (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 4A8986109F for ; Thu, 4 Nov 2021 08:18:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 4A8986109F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=redhat.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-457-9kZY0vJTMK6AwRx8I1OFpA-1; Thu, 04 Nov 2021 04:18:04 -0400 X-MC-Unique: 9kZY0vJTMK6AwRx8I1OFpA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D85895074D; Thu, 4 Nov 2021 08:17:59 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D4A8E5BAF0; Thu, 4 Nov 2021 08:17:52 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 5F31B1806D03; Thu, 4 Nov 2021 08:17:52 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 1A48HomI013819 for ; Thu, 4 Nov 2021 04:17:50 -0400 Received: by smtp.corp.redhat.com (Postfix) id EAEB551E1; Thu, 4 Nov 2021 08:17:49 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast04.extmail.prod.ext.rdu2.redhat.com [10.11.55.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E600151DC for ; Thu, 4 Nov 2021 08:17:47 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 08F3F1064FB0 for ; Thu, 4 Nov 2021 08:17:47 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-530-1lpQFp6VOjKwIe_LaO74cQ-1; Thu, 04 Nov 2021 04:17:43 -0400 X-MC-Unique: 1lpQFp6VOjKwIe_LaO74cQ-1 Received: by verein.lst.de (Postfix, from userid 2407) id 9396E68AA6; Thu, 4 Nov 2021 09:17:40 +0100 (CET) Date: Thu, 4 Nov 2021 09:17:40 +0100 From: Christoph Hellwig To: Eric Sandeen Message-ID: <20211104081740.GA23111@lst.de> References: <20211018044054.1779424-1-hch@lst.de> <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> MIME-Version: 1.0 In-Reply-To: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> User-Agent: Mutt/1.5.17 (2007-11-01) X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-loop: dm-devel@redhat.com Cc: nvdimm@lists.linux.dev, Mike Snitzer , linux-s390@vger.kernel.org, linux-erofs@lists.ozlabs.org, 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 Subject: Re: [dm-devel] futher decouple DAX from block devices X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Nov 03, 2021 at 12:59:31PM -0500, Eric Sandeen wrote: > Christoph, can I ask what the end game looks like, here? If dax is completely > decoupled from block devices, are there user-visible changes? Yes. > If I want to > run fs-dax on a pmem device - what do I point mkfs at, if not a block device? The rough plan is to use the device dax character devices. I'll hopefully have a draft version in the next days. -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel