From: Jeff Moyer <jmoyer@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 0/7] dax, ext4: Synchronous page faults
Date: Thu, 27 Jul 2017 10:09:07 -0400 [thread overview]
Message-ID: <x49zibq3rb0.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20170727131245.28279-1-jack@suse.cz> (Jan Kara's message of "Thu, 27 Jul 2017 15:12:38 +0200")
Jan Kara <jack@suse.cz> writes:
Hi, Jan,
Thanks for looking into this!
> There are couple of open questions with this implementation:
>
> 1) Is it worth the hassle?
> 2) Is S_SYNC good flag to use or should we use a new inode flag?
> 3) VM_FAULT_RO and especially passing of resulting 'pfn' from
> dax_iomap_fault() through filesystem fault handler to dax_pfn_mkwrite() in
> vmf->orig_pte is a bit of a hack. So far I'm not sure how to refactor
> things to make this cleaner.
4) How does an application discover that it is safe to flush from
userspace?
-Jeff
next prev parent reply other threads:[~2017-07-27 14:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 13:12 [RFC PATCH 0/7] dax, ext4: Synchronous page faults Jan Kara
2017-07-27 13:12 ` [PATCH 2/7] dax: Add sync argument to dax_iomap_fault() Jan Kara
[not found] ` <20170727131245.28279-3-jack-AlSwsSmVLrQ@public.gmane.org>
2017-07-27 22:06 ` Ross Zwisler
2017-07-28 9:40 ` Jan Kara
[not found] ` <20170727131245.28279-1-jack-AlSwsSmVLrQ@public.gmane.org>
2017-07-27 13:12 ` [PATCH 1/7] mm: Remove VM_FAULT_HWPOISON_LARGE_MASK Jan Kara
[not found] ` <20170727131245.28279-2-jack-AlSwsSmVLrQ@public.gmane.org>
2017-07-27 21:57 ` Ross Zwisler
2017-08-01 10:52 ` Christoph Hellwig
2017-07-27 13:12 ` [PATCH 3/7] dax: Simplify arguments of dax_insert_mapping() Jan Kara
[not found] ` <20170727131245.28279-4-jack-AlSwsSmVLrQ@public.gmane.org>
2017-07-27 22:09 ` Ross Zwisler
2017-08-01 10:54 ` Christoph Hellwig
2017-07-27 13:12 ` [PATCH 4/7] dax: Make dax_insert_mapping() return VM_FAULT_ state Jan Kara
2017-07-27 22:22 ` Ross Zwisler
2017-07-28 9:43 ` Jan Kara
2017-07-27 13:12 ` [PATCH 5/7] dax, iomap: Add support for synchronous faults Jan Kara
2017-07-27 22:42 ` Ross Zwisler
[not found] ` <20170727224245.GF22000-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-08-01 10:56 ` Christoph Hellwig
2017-07-27 13:12 ` [PATCH 6/7] dax: Implement dax_pfn_mkwrite() Jan Kara
[not found] ` <20170727131245.28279-7-jack-AlSwsSmVLrQ@public.gmane.org>
2017-07-27 22:53 ` Ross Zwisler
2017-07-27 23:04 ` Ross Zwisler
[not found] ` <20170727225322.GG22000-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-07-28 10:37 ` Jan Kara
2017-08-01 10:52 ` [RFC PATCH 0/7] dax, ext4: Synchronous page faults Christoph Hellwig
2017-07-27 13:12 ` [PATCH 7/7] ext4: Support for synchronous DAX faults Jan Kara
2017-07-27 22:57 ` Ross Zwisler
2017-07-27 14:09 ` Jeff Moyer [this message]
2017-07-27 21:57 ` [RFC PATCH 0/7] dax, ext4: Synchronous page faults Ross Zwisler
2017-07-28 2:05 ` Andy Lutomirski
[not found] ` <CALCETrVzxrQ76BXEfo4kcRFyQmxbrMwCLE17yPyTJzz0tUs+Dg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-28 9:38 ` Jan Kara
2017-08-01 11:02 ` Christoph Hellwig
[not found] ` <20170801110241.GE6742-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-08-01 11:26 ` Jan Kara
2017-08-08 0:24 ` Dan Williams
[not found] ` <CAPcyv4hdOsuA6cqRCnOZMLMXvycwZevg06xOVZz3u0kupm2Drw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 10:03 ` Christoph Hellwig
[not found] ` <20170811100327.GD7064-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-08-13 2:44 ` Dan Williams
2017-08-13 9:25 ` Christoph Hellwig
2017-08-13 17:08 ` Dan Williams
2017-08-14 8:30 ` Jan Kara
2017-08-14 14:04 ` Boaz Harrosh
2017-08-14 16:03 ` Dan Williams
2017-08-15 9:06 ` Boaz Harrosh
2017-08-15 9:44 ` Boaz Harrosh
[not found] ` <CAPcyv4jWW5EH8KrGWe-9oAT7RvFryh1ci6CcGeDb-zcOS9QMxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-21 19:57 ` Ross Zwisler
2017-08-17 16:08 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x49zibq3rb0.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luto@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).