linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [GIT PULL] Hole puch vs page cache filling races fixes for 5.14-rc1
Date: Thu, 1 Jul 2021 11:04:28 -0700	[thread overview]
Message-ID: <CAHk-=wiELnOWPLj2g2_JFxEquRXP2GikONXjyeSjv-Mque0Aaw@mail.gmail.com> (raw)
In-Reply-To: <20210701161941.GA29014@quack2.suse.cz>

On Thu, Jul 1, 2021 at 9:19 AM Jan Kara <jack@suse.cz> wrote:
>
> That being said I don't expect the optimization to matter too much
> because in do_read_fault() we first call do_fault_around() which will
> exactly map pages that are already in cache and uptodate

Yeah, I think that ends up saving the situation.

> So do you think the optimization is still worth it despite
> do_fault_around()?

I suspect it doesn't matter that much for performance as you say due
to any filesystem that cares about performance having the "map_pages"
function pointing to filemap_map_pages, but I reacted to it just from
looking at the patch, and it just seems conceptually wrong. Taking the
lock in a situation where it's not actually needed will just cause
problems later when somebody decides that the lock protects something
else entirely.

             Linus

  reply	other threads:[~2021-07-01 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 17:25 [GIT PULL] Hole puch vs page cache filling races fixes for 5.14-rc1 Jan Kara
2021-07-01  1:15 ` Linus Torvalds
2021-07-01 16:19   ` Jan Kara
2021-07-01 18:04     ` Linus Torvalds [this message]
2021-07-06 20:17       ` Jan Kara

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-=wiELnOWPLj2g2_JFxEquRXP2GikONXjyeSjv-Mque0Aaw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).