From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Lokesh Gidra <lokeshgidra@google.com>, Zi Yan <ziy@nvidia.com>,
Barry Song <21cnbao@gmail.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
Peter Xu <peterx@redhat.com>,
Suren Baghdasaryan <surenb@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
android-mm <android-mm@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jann Horn <jannh@google.com>, Rik van Riel <riel@surriel.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [DISCUSSION] Unconditionally lock folios when calling rmap_walk()
Date: Thu, 28 Aug 2025 12:32:12 +0100 [thread overview]
Message-ID: <cc185893-dd85-4571-9d0f-23ca3b8762df@lucifer.local> (raw)
In-Reply-To: <aKxAWqvTxctPoumF@hyeyoo>
On Mon, Aug 25, 2025 at 07:52:10PM +0900, Harry Yoo wrote:
> Adding folio_lock/unlock in folio_referenced() is likely to affect
> reclamation performance. How bad is it? I don't know, need data.
>
> And adding cost only for the uffd case might not be justifiable...
Exactly.
next prev parent reply other threads:[~2025-08-28 11:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 17:29 [DISCUSSION] Unconditionally lock folios when calling rmap_walk() Lokesh Gidra
2025-08-22 17:44 ` Matthew Wilcox
2025-08-22 18:08 ` Lorenzo Stoakes
2025-08-24 4:18 ` Lokesh Gidra
2025-08-24 5:31 ` Harry Yoo
2025-08-24 6:45 ` Lokesh Gidra
2025-08-25 10:52 ` Harry Yoo
2025-08-28 11:32 ` Lorenzo Stoakes [this message]
2025-08-25 15:19 ` David Hildenbrand
2025-08-25 18:46 ` Lokesh Gidra
2025-08-28 12:04 ` Lorenzo Stoakes
2025-08-29 0:23 ` Lokesh Gidra
2025-08-29 8:42 ` David Hildenbrand
2025-08-29 9:04 ` Lorenzo Stoakes
2025-09-02 18:59 ` Lokesh Gidra
2025-09-02 19:01 ` David Hildenbrand
2025-09-02 19:04 ` Lokesh Gidra
2025-08-29 9:01 ` Lorenzo Stoakes
2025-08-26 15:52 ` Lorenzo Stoakes
2025-08-26 22:23 ` Lokesh Gidra
2025-08-28 11:31 ` Lorenzo Stoakes
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=cc185893-dd85-4571-9d0f-23ca3b8762df@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=21cnbao@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=android-mm@google.com \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.com \
/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).