From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-f195.google.com ([209.85.166.195]:54892 "EHLO mail-it1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727951AbeLMT4A (ORCPT ); Thu, 13 Dec 2018 14:56:00 -0500 MIME-Version: 1.0 References: <20181210171318.16998-1-vgoyal@redhat.com> <20181210171318.16998-16-vgoyal@redhat.com> In-Reply-To: <20181210171318.16998-16-vgoyal@redhat.com> From: Dan Williams Date: Thu, 13 Dec 2018 11:55:47 -0800 Message-ID: Subject: Re: [PATCH 15/52] fuse: map virtio_fs DAX window BAR To: vgoyal@redhat.com Cc: linux-fsdevel , Linux Kernel Mailing List , KVM list , Miklos Szeredi , stefanha@redhat.com, dgilbert@redhat.com, sweil@redhat.com, swhiteho@redhat.com Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Dec 10, 2018 at 9:22 AM Vivek Goyal wrote: > > From: Stefan Hajnoczi > > Experimental QEMU code introduces an MMIO BAR for mapping portions of > files in the virtio-fs device. Map this BAR so that FUSE DAX can access > file contents from the host page cache. FUSE DAX sounds terrifying, can you explain a bit more about what this is? > The DAX window is accessed by the fs/dax.c infrastructure and must have > struct pages (at least on x86). Use devm_memremap_pages() to map the > DAX window PCI BAR and allocate struct page. PCI BAR space is not cache coherent, what prevents these pages from being used in paths that would do: object = page_address(pfn_to_page(virtio_fs_pfn)); ...?