The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	tytso@mit.edu, willy@infradead.org, mjguzik@gmail.com,
	david@fromorbit.com
Subject: Re: [PATCH] [v2] filemap: Move prefaulting out of hot write path
Date: Mon, 3 Mar 2025 18:37:01 -0800	[thread overview]
Message-ID: <20250303183701.36624c484c54c2c3c6b470a5@linux-foundation.org> (raw)
In-Reply-To: <20250228203722.CAEB63AC@davehans-spike.ostc.intel.com>

On Fri, 28 Feb 2025 12:37:22 -0800 Dave Hansen <dave.hansen@linux.intel.com> wrote:

> There is a generic anti-pattern that shows up in the VFS and several
> filesystems where the hot write paths touch userspace twice when they
> could get away with doing it once.
> 
> Dave Chinner suggested that they should all be fixed up[1]. I agree[2].
> But, the series to do that fixup spans a bunch of filesystems and a lot
> of people. This patch fixes common code that absolutely everyone uses.
> It has measurable performance benefits[3].
> 
> I think this patch can go in and not be held up by the others.

I'll queue this in mm-hotfixes with a view to sneaking it into 6.14-rcX
as a basis for others to work against.


  reply	other threads:[~2025-03-04  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 20:37 [PATCH] [v2] filemap: Move prefaulting out of hot write path Dave Hansen
2025-03-04  2:37 ` Andrew Morton [this message]
2025-03-10  8:45 ` kernel test robot

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=20250303183701.36624c484c54c2c3c6b470a5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.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