From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Lokesh Gidra <lokeshgidra@google.com>
Cc: Harry Yoo <harry.yoo@oracle.com>, Zi Yan <ziy@nvidia.com>,
Barry Song <21cnbao@gmail.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
Suren Baghdasaryan <surenb@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
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>
Subject: Re: [RFC] Unconditionally lock folios when calling rmap_walk()
Date: Fri, 22 Aug 2025 11:50:14 +0100 [thread overview]
Message-ID: <3972cb48-2684-4ba6-ab78-66460a939929@lucifer.local> (raw)
In-Reply-To: <aKhIL3OguViS9myH@hyeyoo>
Lokesh, this is a mess :/
I've been a reverse mapping co-maintainer for 4 months now, please check
MAINTAINERS before sending this stuff out. It's not really impressive to
learn about this 2nd hand...
Also I cannot get lei to get this mail to me, no matter how hard I try. So
it's _really hard_ for me to respond to this.
And you label this '[RFC]' but I can't find any code (unless it's lost in
the thread somehow). It should be '[DISCUSSION]'.
rmap locking is _extremely_ sensitive and the discussion needs careful
attention.
It's hard for me to even track what's going on here or join the discussion,
could you just please resend, correctly cc'ing the maintainers/reviewers of
rmap, and prefix with '[DISCUSSION]'?
You've already got responses here so we're inevitably going to fork the
conversation, but unfortunately I don't see any way around this, because
I'm going to miss all the conversation that I'm not cc'd on.
Anwyay I simply can't engage on this as-is, and I really _want to_, because
rmap and the locking around it are issues of PRIMARY importance to me.
Please try to make my life easier :)
Thanks, Lorenzo
next prev parent reply other threads:[~2025-08-22 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+EESO6dR5=4zaecmYqQqOX4702wwGSTX=4+Ani_Q9+o+WUnQA@mail.gmail.com>
2025-08-21 4:29 ` Lokesh Gidra
2025-08-21 12:01 ` Barry Song
2025-08-21 16:13 ` Zi Yan
2025-08-21 17:56 ` Lokesh Gidra
2025-08-22 10:36 ` Harry Yoo
2025-08-22 10:50 ` Lorenzo Stoakes [this message]
2025-08-22 17:16 ` Lokesh Gidra
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=3972cb48-2684-4ba6-ab78-66460a939929@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