From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: ljs@kernel.org, liam@infradead.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
qi.zheng@linux.dev, jack@suse.cz, pfalcato@suse.de,
ayushr@modal.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] mm: memory: fix truncation removing mapped folios
Date: Tue, 27 Oct 2026 13:53:34 +0100 [thread overview]
Message-ID: <3c73fe54-68d8-41f3-8f9f-06c4a1891e01@kernel.org> (raw)
In-Reply-To: <f41d0720-ca14-4aa3-a2e4-3ba2de3280d0@linux.alibaba.com>
On 10/27/26 13:50, Baolin Wang wrote:
>
>
> On 10/27/26 6:55 PM, David Hildenbrand (Arm) wrote:
>> On 10/27/26 11:35, Baolin Wang wrote:
>>>
>>>
>>>
>>> Sure.
>>>
>>>
>>> IMHO, I'm not a big fan of adding two pmd_none() checks just to avoid an
>>> uncommon concurrent sync.
>>
>> It's what we already had. We had to: one for handling pmd_none() directly and
>> one for handling zapping while splitting (file THPs).
>>
>> We just managed to let the second also handle the final piece of the former.
>>
>> Anyhow, let's get this fixed.
>>
>> If you think the code is clearer your way (where I disagree)
>
> Fair enough. Though I have a different taste, I'd still like to make the
> maintainer happy.
Don't worry, it's hard to make me unhappy :)
(just a bit overloaded right now)
> I'll send out v6 tomorrow following your suggestion.
>
That looks good. Are you planning on following up with the memory barrier
optimization for smaller folios?
I hope below doesn't end up in some performance degradation.
--
Cheers,
David
next prev parent reply other threads:[~2026-10-27 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 2:19 Baolin Wang
2026-10-27 9:00 ` David Hildenbrand (Arm)
2026-10-27 9:03 ` Baolin Wang
2026-10-27 9:33 ` David Hildenbrand (Arm)
2026-10-27 10:35 ` Baolin Wang
2026-10-27 10:55 ` David Hildenbrand (Arm)
2026-10-27 12:50 ` Baolin Wang
2026-10-27 12:53 ` David Hildenbrand (Arm) [this message]
2026-10-27 13:04 ` Baolin Wang
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=3c73fe54-68d8-41f3-8f9f-06c4a1891e01@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ayushr@modal.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=jack@suse.cz \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.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®