From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 05DCD21250C98 for ; Thu, 16 May 2019 07:23:45 -0700 (PDT) Date: Thu, 16 May 2019 10:23:42 -0400 From: Vivek Goyal Subject: Re: [PATCH v2 12/30] dax: remove block device dependencies Message-ID: <20190516142342.GA31638@redhat.com> References: <20190515192715.18000-1-vgoyal@redhat.com> <20190515192715.18000-13-vgoyal@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: KVM list , linux-nvdimm , Miklos Szeredi , "Dr. David Alan Gilbert" , Linux Kernel Mailing List , Stefan Hajnoczi , linux-fsdevel , Steven Whitehouse List-ID: On Wed, May 15, 2019 at 05:21:51PM -0700, Dan Williams wrote: [..] > It just seems to me that we should stop pretending that the > filesystem-dax facility requires block devices and try to move this > functionality to generically use a dax device across all interfaces. That sounds reasonable and will help with our use case where we don't have the block device at all. Vivek _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm