[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4hCP4E4xPkQx25tqhznon6ADwrYJB1yujkrO-A7LUnsmg@mail.gmail.com>
Date: Tue, 7 May 2019 08:37:01 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Pankaj Gupta <pagupta@...hat.com>
Cc: linux-nvdimm <linux-nvdimm@...ts.01.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
KVM list <kvm@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Qemu Developers <qemu-devel@...gnu.org>,
linux-ext4 <linux-ext4@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
Ross Zwisler <zwisler@...nel.org>,
Vishal L Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
Matthew Wilcox <willy@...radead.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Christoph Hellwig <hch@...radead.org>,
Len Brown <lenb@...nel.org>, Jan Kara <jack@...e.cz>,
"Theodore Ts'o" <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
lcapitulino@...hat.com, Kevin Wolf <kwolf@...hat.com>,
Igor Mammedov <imammedo@...hat.com>,
jmoyer <jmoyer@...hat.com>,
Nitesh Narayan Lal <nilal@...hat.com>,
Rik van Riel <riel@...riel.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
David Hildenbrand <david@...hat.com>,
david <david@...morbit.com>, cohuck@...hat.com,
Xiao Guangrong <xiaoguangrong.eric@...il.com>,
Paolo Bonzini <pbonzini@...hat.com>, kilobyte@...band.pl,
yuval shaia <yuval.shaia@...cle.com>
Subject: Re: [PATCH v7 6/6] xfs: disable map_sync for async flush
On Thu, Apr 25, 2019 at 10:03 PM Pankaj Gupta <pagupta@...hat.com> wrote:
>
> Dont support 'MAP_SYNC' with non-DAX files and DAX files
> with asynchronous dax_device. Virtio pmem provides
> asynchronous host page cache flush mechanism. We don't
> support 'MAP_SYNC' with virtio pmem and xfs.
>
> Signed-off-by: Pankaj Gupta <pagupta@...hat.com>
> ---
> fs/xfs/xfs_file.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Darrick, does this look ok to take through the nvdimm tree?
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index a7ceae90110e..f17652cca5ff 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -1203,11 +1203,14 @@ xfs_file_mmap(
> struct file *filp,
> struct vm_area_struct *vma)
> {
> + struct dax_device *dax_dev;
> +
> + dax_dev = xfs_find_daxdev_for_inode(file_inode(filp));
> /*
> - * We don't support synchronous mappings for non-DAX files. At least
> - * until someone comes with a sensible use case.
> + * We don't support synchronous mappings for non-DAX files and
> + * for DAX files if underneath dax_device is not synchronous.
> */
> - if (!IS_DAX(file_inode(filp)) && (vma->vm_flags & VM_SYNC))
> + if (!daxdev_mapping_supported(vma, dax_dev))
> return -EOPNOTSUPP;
>
> file_accessed(filp);
> --
> 2.20.1
>
Powered by blists - more mailing lists