From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] dax: adding fsync/msync support for device DAX
Date: Thu, 5 Apr 2018 08:10:38 -0700 [thread overview]
Message-ID: <20180405151038.GB11834@infradead.org> (raw)
In-Reply-To: <x49efjtwvgh.fsf@segfault.boston.devel.redhat.com>
On Thu, Apr 05, 2018 at 10:59:10AM -0400, Jeff Moyer wrote:
> So, I also hate this (note that this is already in place today for fs
> dax). You have an operation to make things persistent, and another one
> to *really* make things persistent. It makes no sense to me. I have no
> idea how to communicate that to application developers. When do you
> force things out to the smallest failure domain?
>
> The arguments I've heard are that ADR failures may happen due to a
> variety of factors, and that an application (or file system) can make
> sure that critical (meta)data is available after a crash by flushing to
> the smallest failure domain. Presumably, this would be a
> lower-frequency event (only for metadata changes, etc).
Which meansit should not abuse fsync but have a special interface
just for that IFF we trust ADR. IFF we don't trust it anyway fsync
absolutely is the right interface, but then we shouldn't offer MAP_SYNC.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-04-05 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 22:01 [PATCH] dax: adding fsync/msync support for device DAX Dave Jiang
2018-04-05 0:03 ` Dan Williams
2018-04-05 7:23 ` Christoph Hellwig
2018-04-05 7:56 ` Dan Williams
2018-04-05 8:01 ` Christoph Hellwig
2018-04-05 14:59 ` Jeff Moyer
2018-04-05 15:10 ` Christoph Hellwig [this message]
2018-04-05 22:17 ` Dan Williams
2018-04-06 7:03 ` Christoph Hellwig
2018-04-06 22:41 ` Dan Williams
2018-04-09 9:32 ` Christoph Hellwig
2018-04-11 16:06 ` Jeff Moyer
2018-04-11 16:27 ` Dan Williams
2018-04-11 17:27 ` Jeff Moyer
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=20180405151038.GB11834@infradead.org \
--to=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.