From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>, Ted Ts'o <tytso@mit.edu>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Do we need to unrevert "fs: do not prefault sys_write() user buffer pages"?
Date: Tue, 22 Jun 2021 19:23:10 +0100 [thread overview]
Message-ID: <YNIqjhsvEms6+vk9@casper.infradead.org> (raw)
In-Reply-To: <CAHk-=wicC9ZTNNH1E-oHebcT3+r4Q4Wf1tXBindXrCdotj20Gg@mail.gmail.com>
On Tue, Jun 22, 2021 at 11:07:56AM -0700, Linus Torvalds wrote:
> On Tue, Jun 22, 2021 at 11:05 AM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > Huh? Last I checked, the fault_in_readable actually read a byte from
> > the page. It has to wait for the read to complete before that can
> > happen.
>
> Yeah, we don't have any kind of async fault-in model.
>
> I'm not sure how that would even look. I don't think it would
> necessarily be *impossible* (special marker in the exception table to
> let the fault code know that this is a "prepare" fault), but it would
> be pretty challenging.
It wouldn't be _that_ bad necessarily. filemap_fault:
page = find_get_page(mapping, offset);
...
} else if (!page) {
fpin = do_sync_mmap_readahead(vmf);
... and we could return at that point if the flag was set. There'd be
some more details to fill in (if there's a !uptodate page in the page
cache, don't wait for it), but it might not be too bad.
next prev parent reply other threads:[~2021-06-22 18:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 15:20 Do we need to unrevert "fs: do not prefault sys_write() user buffer pages"? David Howells
2021-06-22 15:27 ` Al Viro
2021-06-22 15:36 ` Al Viro
2021-06-22 17:25 ` Matthew Wilcox
2021-06-22 17:39 ` Linus Torvalds
2021-06-22 17:55 ` David Howells
2021-06-22 18:04 ` Matthew Wilcox
2021-06-22 18:07 ` Linus Torvalds
2021-06-22 18:16 ` Nadav Amit
2021-06-22 18:23 ` Matthew Wilcox [this message]
2021-06-22 18:28 ` Linus Torvalds
2021-06-22 18:36 ` Matthew Wilcox
2021-06-22 18:51 ` Nadav Amit
2021-06-22 18:57 ` Linus Torvalds
2021-06-22 18:23 ` David Howells
2021-06-22 18:32 ` Linus Torvalds
2021-06-22 18:13 ` David Howells
2021-06-22 15:32 ` Linus Torvalds
2021-06-22 15:53 ` Linus Torvalds
2021-06-22 15:32 ` Matthew Wilcox
2021-06-22 16:27 ` David Howells
2021-06-22 21:55 ` David Laight
2021-06-22 22:04 ` Matthew Wilcox
2021-06-22 22:31 ` David Laight
2021-06-22 22:20 ` Dave Chinner
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=YNIqjhsvEms6+vk9@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).