From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Vijay Chidambaram <vijay@cs.utexas.edu>,
lsf-pc@lists.linux-foundation.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Jan Kara <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jayashree Mohan <jaya@cs.utexas.edu>,
Filipe Manana <fdmanana@suse.com>, Chris Mason <clm@fb.com>,
lwn@lwn.net
Subject: Re: [TOPIC] Extending the filesystem crash recovery guaranties contract
Date: Wed, 8 May 2019 23:31:00 -0400 [thread overview]
Message-ID: <20190509033100.GB29703@mit.edu> (raw)
In-Reply-To: <20190509025845.GV1454@dread.disaster.area>
On Thu, May 09, 2019 at 12:58:45PM +1000, Dave Chinner wrote:
>
> SOMC does not defining crash consistency rules - it defines change
> dependecies and how ordering and atomicity impact the dependency
> graph. How other people have interpreted that is out of my control.
Fine; but it's a specific set of the crash consistency rules which I'm
objecting to; it's not a promise that I think I want to make. (And
before you blindly sign on the bottom line, I'd suggest that you read
it very carefully before deciding whether you want to agree to those
consistency rules as something that XFS will have honor forever. The
way I read it, it's goes beyond what you've articulated as SOMC.)
> A new syscall with essentially the same user interface doesn't
> guarantee that these implementation problems will be solved.
Well, it makes it easier to send all of the requests to the file
system in a single bundle. I'd also argue that it's simpler and
easier for an application to use a fsync2() interface as I sketched
out than trying to use the whole AIO or io_uring machinery.
> So it's essentially identical to the AIO_FSYNC interface, except
> that it is synchronous.
Pretty much, yes.
> Sheesh! Did LSFMM include a free lobotomy for participants, or
> something?
Well, we missed your presence, alas. No doubt your attendance would
have improved the discussion.
Cheers,
- Ted
next prev parent reply other threads:[~2019-05-09 3:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 21:00 [TOPIC] Extending the filesystem crash recovery guaranties contract Amir Goldstein
2019-05-02 16:12 ` Amir Goldstein
2019-05-02 17:11 ` Vijay Chidambaram
2019-05-02 17:39 ` Amir Goldstein
2019-05-03 2:30 ` Theodore Ts'o
2019-05-03 3:15 ` Vijay Chidambaram
2019-05-03 9:45 ` Theodore Ts'o
2019-05-04 0:17 ` Vijay Chidambaram
2019-05-04 1:43 ` Theodore Ts'o
2019-05-07 18:38 ` Jan Kara
2019-05-03 4:16 ` Amir Goldstein
2019-05-03 9:58 ` Theodore Ts'o
2019-05-03 14:18 ` Amir Goldstein
2019-05-09 2:36 ` Dave Chinner
2019-05-09 1:43 ` Dave Chinner
2019-05-09 2:20 ` Theodore Ts'o
2019-05-09 2:58 ` Dave Chinner
2019-05-09 3:31 ` Theodore Ts'o [this message]
2019-05-09 5:19 ` Darrick J. Wong
2019-05-09 5:02 ` Vijay Chidambaram
2019-05-09 5:37 ` Darrick J. Wong
2019-05-09 15:46 ` Theodore Ts'o
2019-05-09 8:47 ` Amir Goldstein
2019-05-02 21:05 ` Darrick J. Wong
2019-05-02 22:19 ` Amir Goldstein
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=20190509033100.GB29703@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fdmanana@suse.com \
--cc=jack@suse.cz \
--cc=jaya@cs.utexas.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=lwn@lwn.net \
--cc=vijay@cs.utexas.edu \
/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).