From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Avi <thnkslprpt@gmail.com>
Cc: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
akpm@linux-foundation.org, rppt@kernel.org, peterx@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
liam@infradead.org, mhocko@suse.com, surenb@google.com,
vbabka@kernel.org
Subject: Re: [PATCH] mm: skip temporary folio allocation for anonymous UFFD missing faults
Date: Fri, 20 Nov 2026 09:38:36 +0100 [thread overview]
Message-ID: <da01ae71-8b99-42b3-9a46-d7e39c1eb981@kernel.org> (raw)
In-Reply-To: <CA+jvY9HQp6iDPGDTuVqrQNnw0ENDDq46_AwZqzcjXNcyFWqPsA@mail.gmail.com>
On 11/20/26 05:20, Avi wrote:
> Hi David - the real motivation is very simple - avoiding the wasted
> allocation (if possible).
> That's it.
Just to clarify: we are all right now completely under water with fixes.
Optimizations "because we can" are not heplful. They cause more stress on
maintainers and reviewers without possibly benefiting anybody in practice.
But that's nothing new: we always required a good motivation in order to spend
our precious time on proposed changes. Because maintainer+reviewer time was
always a limiting factor.
While your changes might optimize some uffd workloads, they make the kernel code
more complicated.
"Because we can" is not sufficient motivation to do that.
IOW, if you don't actively run into a problem, there is not actually something
broken, or you have a real use case that needs solving in core-kernel code,
changes are high that your submissions will be dismissed.
Because we simply don't have the capacity to engage with that, sorry.
--
Cheers,
David
prev parent reply other threads:[~2026-11-20 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 18:00 Avi Weiss
2026-11-19 18:22 ` Lorenzo Stoakes (ARM)
2026-11-19 19:31 ` Avi
2026-11-19 22:34 ` David Hildenbrand (Arm)
2026-11-20 4:20 ` Avi
2026-11-20 8:38 ` David Hildenbrand (Arm) [this message]
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=da01ae71-8b99-42b3-9a46-d7e39c1eb981@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=thnkslprpt@gmail.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®