[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49sgjf1t7n.fsf@segfault.boston.devel.redhat.com>
Date: Wed, 12 Feb 2020 14:49:48 -0500
From: Jeff Moyer <jmoyer@...hat.com>
To: Ira Weiny <ira.weiny@...el.com>
Cc: linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Dave Chinner <david@...morbit.com>,
Christoph Hellwig <hch@....de>,
"Theodore Y. Ts'o" <tytso@....edu>, Jan Kara <jack@...e.cz>,
linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v3 00/12] Enable per-file/directory DAX operations V3
Ira Weiny <ira.weiny@...el.com> writes:
> On Mon, Feb 10, 2020 at 10:15:47AM -0500, Jeff Moyer wrote:
>> Hi, Ira,
>>
>> Could you please include documentation patches as part of this series?
>
> I do have an update to the vfs.rst doc in
>
> fs: Add locking for a dynamic DAX state
>
> I'm happy to do more but was there something specific you would like to see?
> Or documentation in xfs perhaps?
Sorry, I was referring to your statx man page addition. It would be
nice if we could find a home for the information in your cover letter,
too. Right now, I'm not sure how application developers are supposed to
figure out how to use the per-inode settings.
If I read your cover letter correctly, the mount option overrides any
on-disk setting. Is that right? Given that we document the dax mount
option as "the way to get dax," it may be a good idea to allow for a
user to selectively disable dax, even when -o dax is specified. Is that
possible?
-Jeff
Powered by blists - more mailing lists