From: Hannes Reinecke <hare@suse.com>
To: Matthew Wilcox <willy6545@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Project Banbury
Date: Tue, 18 Sep 2018 10:17:10 +0200 [thread overview]
Message-ID: <1e7100f5-5e45-633f-09b2-4982547789a5@suse.com> (raw)
In-Reply-To: <CAFhKne-T1bTDE0QtDXxWBn7Quyk_kHes_XX=1yQAdMxVVx4zDg@mail.gmail.com>
On 09/16/2018 02:45 PM, Matthew Wilcox wrote:
> Unfortunately I won't be in Edinburgh. My understanding was that the
> tech topics are for Plumbers. Since the user space component is
> probably the more interesting and complex component, Plumbers is
> probably the better conference for a discussion anyway.
>
Au contraire.
ATM most filesystems are not able to report any I/O error directly to
the application due to internal caching. An I/O error will only ever be
seen once the cached data is written to disk, but by then the fs has
already acknowledged the write to the application, so there literally is
no way of how we could signal the I/O error (other than setting the fs
read-only).
So from that it might be possible to switch to an asynchronous model of
signalling I/O errors much like DAX does nowadays.
IE we could signal errors to the filesystem via asynchronous methods,
and do away with the current synchronous model.
I guess some further discussion is warranted here.
Sadly I can't go to Vancouver, so we'll need to find another venue; LSF
next year?
Cheers,
Hannes
next prev parent reply other threads:[~2018-09-18 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 17:28 [Ksummit-discuss] [TECH TOPIC] Project Banbury Matthew Wilcox
2018-09-16 10:53 ` Hannes Reinecke
2018-09-16 12:45 ` Matthew Wilcox
2018-09-18 8:17 ` Hannes Reinecke [this message]
2018-09-16 16:03 ` Laurent Pinchart
2018-09-16 16:25 ` Linus Torvalds
2018-09-16 16:37 ` James Bottomley
2018-09-16 19:25 ` Theodore Y. Ts'o
2018-09-16 23:58 ` David Howells
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=1e7100f5-5e45-633f-09b2-4982547789a5@suse.com \
--to=hare@suse.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=willy6545@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).