Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
	akpm@linux-foundation.org, ljs@kernel.org
Cc: riel@surriel.com, liam@infradead.org, vbabka@kernel.org,
	harry@kernel.org, jannh@google.com, lance.yang@linux.dev,
	qi.zheng@linux.dev, pfalcato@suse.de, ayushr@modal.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: synchronize with PTE table reclaim for all folio sizes
Date: Mon, 16 Nov 2026 15:09:25 +0100	[thread overview]
Message-ID: <41f77b04-432f-40c8-96da-6a8be69a730f@kernel.org> (raw)
In-Reply-To: <01d59bbc-46d4-4da2-805c-bf540d50eb37@linux.alibaba.com>

On 11/16/26 14:34, Baolin Wang wrote:
> 
> 
> On 11/16/26 8:03 PM, David Hildenbrand (Arm) wrote:
>> On 11/16/26 04:44, Baolin Wang wrote:
>>>
>>>
>>>
>>> I hope we can merge this fix first if no other objections. As I replied
>>> to Barry, whether to set TTU_SYNC for small folios should be done in a
>>> separate patch (this is a pre-existing issue) with proper measurement
>>> (though it may be hard to measure the actual impact). What do you think?
>>
>> Can you update the patch description to include some of the performance aspects
>> and planned next steps?
> 
> Sure.
> 
> However, regarding performance aspects, I'm not sure what kind of 
> testing you expect. Since this fixes a uncommon concurrent race, do you 
> want performance data under that race condition, or impact on common 
> paths like try_to_unmap/try_to_migrate()?

Right, I think you had some numbers here that would be worthwhile to include:

https://lore.kernel.org/r/453e2c18-4e79-4db2-b565-1af881925f08@linux.alibaba.com

-- 
Cheers,

David


      reply	other threads:[~2026-11-16 14:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  2:56 [PATCH] mm: synchronize with PTE table reclaim for all folio sizes Baolin Wang
2026-11-05  3:22 ` Qi Zheng
2026-11-05  4:54 ` Lance Yang
2026-11-05  5:48   ` Lance Yang
2026-11-05  9:00     ` Baolin Wang
2026-11-05 10:06       ` David Hildenbrand (Arm)
2026-11-05 11:18         ` Baolin Wang
2026-11-05 13:22         ` Lance Yang
2026-11-05 19:35           ` David Hildenbrand (Arm)
2026-11-06  1:57           ` Baolin Wang
2026-11-06  2:33             ` Lance Yang
2026-11-06  2:54               ` Baolin Wang
2026-11-07 20:05                 ` David Hildenbrand (Arm)
2026-11-06  6:24       ` Barry Song
2026-11-06  8:54         ` Baolin Wang
2026-11-06  9:15           ` Lance Yang
2026-11-06  9:29             ` Lance Yang
2026-11-06  9:50               ` Baolin Wang
2026-11-06  9:56           ` Barry Song
2026-11-06 13:56             ` Baolin Wang
2026-11-10  6:23               ` Baolin Wang
2026-11-10  8:54                 ` Barry Song
2026-11-05 11:37 ` Pedro Falcato
2026-11-06  2:12   ` Baolin Wang
2026-11-07 19:58     ` David Hildenbrand (Arm)
2026-11-09  3:39       ` Baolin Wang
2026-11-09  4:27         ` Barry Song
2026-11-10  3:48           ` Baolin Wang
2026-11-13 17:39 ` David Hildenbrand (Arm)
2026-11-16  3:44   ` Baolin Wang
2026-11-16 12:03     ` David Hildenbrand (Arm)
2026-11-16 13:34       ` Baolin Wang
2026-11-16 14:09         ` 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=41f77b04-432f-40c8-96da-6a8be69a730f@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ayushr@modal.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=harry@kernel.org \
    --cc=jannh@google.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=qi.zheng@linux.dev \
    --cc=riel@surriel.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