xfs
[Top] [All Lists]

Re: [PATCH v2 2/3] mm, dax: add VM_DAX flag for DAX VMAs

To: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Subject: Re: [PATCH v2 2/3] mm, dax: add VM_DAX flag for DAX VMAs
From: Dan Williams <dan.j.williams@xxxxxxxxx>
Date: Thu, 15 Sep 2016 10:44:53 -0700
Cc: Christoph Hellwig <hch@xxxxxx>, "linux-nvdimm@xxxxxxxxxxxx" <linux-nvdimm@xxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Nicholas Piggin <npiggin@xxxxxxxxx>, XFS Developers <xfs@xxxxxxxxxxx>, Linux MM <linux-mm@xxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PzMXKaAJ7UqEj46I69YOFZw+9vRGqC5sa8sagNQCCaY=; b=xn/thOgFCKdnPVJO+eRVkXwCGHmG1q96DeSxkfKS9IfQqoOAOMc0nXZgX/NkHn2qes g4GLTgOX/rYzVcEdX5QHi8P2lnw0P2GxpxRvPXmxZh4pu9RCg4P77YcDKPkkKxP33A7c MHWI9kZDU96Md6ZV6/+0eWcN04tIRWpcNfuyg5+RPgd28p5mJHEq5AomzCxjV5UnfyaE +E44vaHo7aQF+QLUge9C0Kl/N1/ywI+0IiztARBR4tKhh+WPw/gwwzKFyibqytmkRsRX umiwcocL7ZqvQ/o0vavdawJyQLS7H1dekrB9T6M7axkgBQInGwtPV8iO4LbcVcI8EXZk pj6w==
In-reply-to: <20160915170942.GJ9314@xxxxxxxxxxxxxxxx>
References: <147392246509.9873.17750323049785100997.stgit@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <147392247875.9873.4205533916442000884.stgit@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20160915082615.GA9772@xxxxxx> <CAPcyv4jTw3cXpmmJRh7t16Xy2uYofDe+fJ+X_jnz+Q=o0uGneg@xxxxxxxxxxxxxx> <20160915170942.GJ9314@xxxxxxxxxxxxxxxx>
On Thu, Sep 15, 2016 at 10:09 AM, Darrick J. Wong
<darrick.wong@xxxxxxxxxx> wrote:
> On Thu, Sep 15, 2016 at 10:01:03AM -0700, Dan Williams wrote:
>> On Thu, Sep 15, 2016 at 1:26 AM, Christoph Hellwig <hch@xxxxxx> wrote:
>> > On Wed, Sep 14, 2016 at 11:54:38PM -0700, Dan Williams wrote:
>> >> The DAX property, page cache bypass, of a VMA is only detectable via the
>> >> vma_is_dax() helper to check the S_DAX inode flag.  However, this is
>> >> only available internal to the kernel and is a property that userspace
>> >> applications would like to interrogate.
>> >
>> > They have absolutely no business knowing such an implementation detail.
>>
>> Hasn't that train already left the station with FS_XFLAG_DAX?
>
> Seeing as FS_IOC_FSGETXATTR is a "generic" ioctl now, why not just
> implement it for all the DAX fses and block devices?  Aside from xflags,
> the other fields are probably all zero for non-xfs (aside from project
> quota id I guess).
>
> (Yeah, sort of awkward, I know...)

It would solve the problem at hand, I'll take a look.

<Prev in Thread] Current Thread [Next in Thread>