From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sandeen.net (sandeen.net [63.231.237.45]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 47AAC2C98 for ; Wed, 3 Nov 2021 18:07:54 +0000 (UTC) Received: from [10.0.0.146] (liberator.sandeen.net [10.0.0.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by sandeen.net (Postfix) with ESMTPSA id 2B0BF14627D; Wed, 3 Nov 2021 12:57:54 -0500 (CDT) Message-ID: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> Date: Wed, 3 Nov 2021 12:59:31 -0500 Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Content-Language: en-US To: Christoph Hellwig Cc: 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 References: <20211018044054.1779424-1-hch@lst.de> From: Eric Sandeen Subject: Re: futher decouple DAX from block devices In-Reply-To: <20211018044054.1779424-1-hch@lst.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/17/21 11:40 PM, Christoph Hellwig wrote: > Hi Dan, > > this series cleans up and simplifies the association between DAX and block > devices in preparation of allowing to mount file systems directly on DAX > devices without a detour through block devices. Christoph, can I ask what the end game looks like, here? If dax is completely decoupled from block devices, are there user-visible changes? If I want to run fs-dax on a pmem device - what do I point mkfs at, if not a block device? Thanks, -Eric 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 92ADCC433F5 for ; Wed, 3 Nov 2021 18:08: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 05E046112E for ; Wed, 3 Nov 2021 18:08:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 05E046112E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sandeen.net 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 4Hkvrn5J4Sz2yPq for ; Thu, 4 Nov 2021 05:08:09 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=sandeen.net (client-ip=63.231.237.45; helo=sandeen.net; envelope-from=sandeen@sandeen.net; receiver=) X-Greylist: delayed 498 seconds by postgrey-1.36 at boromir; Thu, 04 Nov 2021 05:07:55 AEDT Received: from sandeen.net (sandeen.net [63.231.237.45]) by lists.ozlabs.org (Postfix) with ESMTP id 4HkvrW0974z2ynt for ; Thu, 4 Nov 2021 05:07:54 +1100 (AEDT) Received: from [10.0.0.146] (liberator.sandeen.net [10.0.0.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by sandeen.net (Postfix) with ESMTPSA id 2B0BF14627D; Wed, 3 Nov 2021 12:57:54 -0500 (CDT) Message-ID: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> Date: Wed, 3 Nov 2021 12:59:31 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Content-Language: en-US To: Christoph Hellwig References: <20211018044054.1779424-1-hch@lst.de> From: Eric Sandeen Subject: Re: futher decouple DAX from block devices In-Reply-To: <20211018044054.1779424-1-hch@lst.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" On 10/17/21 11:40 PM, Christoph Hellwig wrote: > Hi Dan, > > this series cleans up and simplifies the association between DAX and block > devices in preparation of allowing to mount file systems directly on DAX > devices without a detour through block devices. Christoph, can I ask what the end game looks like, here? If dax is completely decoupled from block devices, are there user-visible changes? If I want to run fs-dax on a pmem device - what do I point mkfs at, if not a block device? Thanks, -Eric 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 69D6BC433F5 for ; Wed, 3 Nov 2021 18:08:08 +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 B391460F90 for ; Wed, 3 Nov 2021 18:08:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org B391460F90 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sandeen.net 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-MtOF3V0rPJKPsIzuAunUZg-1; Wed, 03 Nov 2021 14:08:05 -0400 X-MC-Unique: MtOF3V0rPJKPsIzuAunUZg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 741BE6972D; Wed, 3 Nov 2021 18:08:00 +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 B3E56197FC; Wed, 3 Nov 2021 18:07:59 +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 1E86F1800B9E; Wed, 3 Nov 2021 18:07:58 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 1A3I7t1x027151 for ; Wed, 3 Nov 2021 14:07:56 -0400 Received: by smtp.corp.redhat.com (Postfix) id CBB474010FE5; Wed, 3 Nov 2021 18:07:55 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast02.extmail.prod.ext.rdu2.redhat.com [10.11.55.18]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C61DC40CFD07 for ; Wed, 3 Nov 2021 18:07:55 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) (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 B18E0800B26 for ; Wed, 3 Nov 2021 18:07:55 +0000 (UTC) Received: from sandeen.net (sandeen.net [63.231.237.45]) by relay.mimecast.com with ESMTP id us-mta-452-2jsANpYdP5qDg0W2sEdFnA-1; Wed, 03 Nov 2021 14:07:54 -0400 X-MC-Unique: 2jsANpYdP5qDg0W2sEdFnA-1 Received: from [10.0.0.146] (liberator.sandeen.net [10.0.0.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by sandeen.net (Postfix) with ESMTPSA id 2B0BF14627D; Wed, 3 Nov 2021 12:57:54 -0500 (CDT) Message-ID: <21ff4333-e567-2819-3ae0-6a2e83ec7ce6@sandeen.net> Date: Wed, 3 Nov 2021 12:59:31 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 To: Christoph Hellwig References: <20211018044054.1779424-1-hch@lst.de> From: Eric Sandeen In-Reply-To: <20211018044054.1779424-1-hch@lst.de> 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.84 on 10.11.54.1 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 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.11 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-Language: en-US Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" On 10/17/21 11:40 PM, Christoph Hellwig wrote: > Hi Dan, > > this series cleans up and simplifies the association between DAX and block > devices in preparation of allowing to mount file systems directly on DAX > devices without a detour through block devices. Christoph, can I ask what the end game looks like, here? If dax is completely decoupled from block devices, are there user-visible changes? If I want to run fs-dax on a pmem device - what do I point mkfs at, if not a block device? Thanks, -Eric -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel