From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, linux-afs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] afs: Fixes
Date: Sat, 25 Nov 2017 22:35:43 +0000 [thread overview]
Message-ID: <23134.1511649343@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+55aFz2Cs+TizSRZF1hYaGak++ehs4Kyb4u__n=aOJh+G_=1w@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> So I see in the commit message why afs needs to do this, but it's
> worth pointing out that it's
>
> (a) impossible to avoid the "inconsistent data" case for writable mmap'ed
> pages
Doesn't clear_page_dirty_for_io() write-protect the PTE for the page to be
written out, in which case ->page_mkwrite() will get called again before the
page is redirtied?
> (b) can cause some really nasty latency issues
True, but I think the most common case is a file being opened, written start
to finish and then closed. Actually, the worst-handled thing I've seen is a
shell script appending a bunch of things to a file because ->flush() syncs the
file each time it is closed:-/
What would you recommend instead? I'm currently trying and keep track of what
needs to be written so that I only write what's changed to the server, rather
than writing only whole pages.
David
next prev parent reply other threads:[~2017-11-25 22:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 14:22 David Howells
2017-11-25 18:05 ` Linus Torvalds
2017-11-25 22:35 ` David Howells [this message]
2017-11-25 22:48 ` Dave Chinner
2017-11-25 22:55 ` Linus Torvalds
2017-11-25 23:19 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2020-10-29 14:07 [GIT PULL] afs fixes David Howells
2020-10-29 17:31 ` pr-tracker-bot
2020-04-13 14:50 [GIT PULL] afs: Fixes David Howells
2020-04-13 15:13 ` David Howells
2020-04-14 19:05 ` pr-tracker-bot
2019-08-22 13:10 David Howells
2019-08-22 18:30 ` pr-tracker-bot
2019-08-14 14:18 David Howells
2019-08-14 22:35 ` pr-tracker-bot
2019-08-14 14:15 David Howells
2019-06-26 13:39 [GIT PULL] AFS fixes David Howells
2019-06-28 0:45 ` pr-tracker-bot
2019-06-26 8:50 David Howells
2019-06-26 13:38 ` David Howells
2019-04-18 9:17 [GIT PULL] afs: Fixes David Howells
2019-04-18 15:20 ` pr-tracker-bot
2018-05-14 21:25 David Howells
2017-03-17 15:29 [GIT PULL] AFS fixes David Howells
2017-03-17 19:23 ` Linus Torvalds
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=23134.1511649343@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome