From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] vfs.git iov_iter
Date: Tue, 12 Mar 2019 14:04:34 -0700 [thread overview]
Message-ID: <CAHk-=wi4vqTpOa3EZZ6Qx0fUL7Tn=NsYZoTqpf03UuNVAirsJQ@mail.gmail.com> (raw)
In-Reply-To: <20190311004146.GI2217@ZenIV.linux.org.uk>
On Sun, Mar 10, 2019 at 5:41 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> A couple of iov_iter patches - Christoph's crapectomy (the last
> remaining user of iov_for_each() went away with lustre, IIRC) and Eric'c
> optimization of sanity checks.
I certainly heartily approve of making page_copy_sane() be less insane
than it used to be.
That said - has the warning that it has triggered lately?
If that sanity check still shows up in profiles as a performance
problem, maybe the whole thing could at least be made dependent on
some sanity checking option to get rid of it entirely for the common
case?
Linus
next prev parent reply other threads:[~2019-03-12 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 0:41 [git pull] vfs.git iov_iter Al Viro
2019-03-12 21:04 ` Linus Torvalds [this message]
2019-03-12 22:20 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2017-11-17 2:50 Al Viro
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='CAHk-=wi4vqTpOa3EZZ6Qx0fUL7Tn=NsYZoTqpf03UuNVAirsJQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).