From: Michal Hocko <mhocko@suse.com>
To: "Liam R. Howlett" <liam@infradead.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Minchan Kim <minchan@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
akpm@linux-foundation.org, hca@linux.ibm.com,
linux-s390@vger.kernel.org, brauner@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
timmurray@google.com, "Liam R. Howlett" <Liam.Howlett@oracle.com>
Subject: Re: [PATCH v1 2/3] mm: process_mrelease: skip LRU movement for exclusive file folios
Date: Wed, 13 May 2026 08:47:15 +0200 [thread overview]
Message-ID: <agQec_L2TXtaXOEo@tiehlicka> (raw)
In-Reply-To: <7g5g57jbll5joujbwjb4osqhdwqd4yzc54wmoi7ftx4a4chuax@xtxyljtqaodp>
On Fri 08-05-26 22:57:31, Liam R. Howlett wrote:
> We can safely drop the flag now if you want to, because everything has
> to deal with an empty vma tree anyways - a race can occur between a call
> to unmap everything and the task seg faulting.
Let's just drop it if it doesn't sever any real need anymore.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2026-05-13 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae-Zu-VAzAA7SdLa@tiehlicka>
[not found] ` <ae_roPR64e6sY_fN@google.com>
[not found] ` <afBaJLLFigkdszov@tiehlicka>
[not found] ` <afFco71vwmpQy3pk@google.com>
[not found] ` <afG-4hq7Hr62Uu6J@tiehlicka>
[not found] ` <7f98f461-62a7-455d-a7a8-cb8928465946@kernel.org>
[not found] ` <afHeXY-yeTwmURWh@tiehlicka>
[not found] ` <4a612d63-2838-40f5-ab67-79bf35dd3a56@kernel.org>
[not found] ` <afIZQOtaBabeHtCc@tiehlicka>
[not found] ` <b2d9fe2b-abb0-49d1-8056-ac93aa232bbb@kernel.org>
2026-05-08 20:57 ` [PATCH v1 2/3] mm: process_mrelease: skip LRU movement for exclusive file folios Liam R. Howlett
2026-05-11 13:05 ` David Hildenbrand (Arm)
2026-05-13 6:47 ` Michal Hocko [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=agQec_L2TXtaXOEo@tiehlicka \
--to=mhocko@suse.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=hca@linux.ibm.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=surenb@google.com \
--cc=timmurray@google.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