From: Matthew Wilcox <willy@infradead.org>
To: "Garg, Shivank" <shivankg@amd.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Zach O'Keefe <zokeefe@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
Branden Moore <Branden.Moore@amd.com>
Subject: Re: [PATCH 1/2] mm/khugepaged: do synchronous writeback for MADV_COLLAPSE
Date: Mon, 10 Nov 2025 14:28:53 +0000 [thread overview]
Message-ID: <aRH2pdhMBQ-20IC9@casper.infradead.org> (raw)
In-Reply-To: <39c8a4ed-53b5-48e3-baea-f67cc1e8be4f@amd.com>
On Mon, Nov 10, 2025 at 07:50:17PM +0530, Garg, Shivank wrote:
> The issue is copying those binary to a freshly mounted filesystem.
> The page cache folios remain dirty until background writeback completes.
>
> Reproduces 100% for me: fresh XFS/EXT4 mount -> copy binary -> execute -> MADV_COLLAPSE fails.
Yes, but this is an uncommon thing to do. Really, it's the kind of
thing you do when you're testing something (like, whether ext4 supports
large folios, and whether that yields a performance improvement).
It's more reasonable to change userspace than the kernel to solve this
problem you're having.
next prev parent reply other threads:[~2025-11-10 14:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:32 [PATCH 1/2] mm/khugepaged: do synchronous writeback for MADV_COLLAPSE Shivank Garg
2025-11-10 11:32 ` [PATCH 2/2] mm/khugepaged: return EAGAIN for transient dirty pages in MADV_COLLAPSE Shivank Garg
2025-11-10 11:56 ` Lorenzo Stoakes
2025-11-19 10:25 ` Garg, Shivank
2025-11-19 18:16 ` Lorenzo Stoakes
2025-11-20 7:03 ` Garg, Shivank
2025-11-10 13:46 ` Dev Jain
2025-11-19 7:00 ` Garg, Shivank
2025-11-10 12:01 ` [PATCH 1/2] mm/khugepaged: do synchronous writeback for MADV_COLLAPSE Lorenzo Stoakes
2025-11-10 13:07 ` Garg, Shivank
2025-11-10 13:22 ` Lorenzo Stoakes
2025-11-10 16:06 ` Lorenzo Stoakes
2025-11-10 16:55 ` Zi Yan
2025-11-10 19:40 ` Garg, Shivank
2025-11-10 19:48 ` Lorenzo Stoakes
2025-11-10 19:53 ` Lorenzo Stoakes
2025-11-10 21:16 ` Lorenzo Stoakes
2025-11-10 21:56 ` Zi Yan
2025-11-10 22:03 ` Lorenzo Stoakes
2025-11-11 5:26 ` Garg, Shivank
2025-11-10 13:24 ` Dev Jain
2025-11-10 13:36 ` Lorenzo Stoakes
2025-11-11 3:41 ` Dev Jain
2025-11-10 13:47 ` Matthew Wilcox
2025-11-10 13:52 ` Lorenzo Stoakes
2025-11-10 14:17 ` Matthew Wilcox
2025-11-10 14:20 ` Garg, Shivank
2025-11-10 14:23 ` Lorenzo Stoakes
2025-11-10 14:28 ` Matthew Wilcox [this message]
2025-11-11 5:58 ` Garg, Shivank
2025-11-13 15:30 ` David Hildenbrand (Red Hat)
2025-11-10 14:00 ` David Hildenbrand (Red Hat)
2025-11-10 14:03 ` Matthew Wilcox
2025-11-10 14:05 ` Lorenzo Stoakes
2025-11-10 14:54 ` David Hildenbrand (Red Hat)
2025-11-13 14:21 ` kernel test robot
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=aRH2pdhMBQ-20IC9@casper.infradead.org \
--to=willy@infradead.org \
--cc=Branden.Moore@amd.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=npache@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=shivankg@amd.com \
--cc=ziy@nvidia.com \
--cc=zokeefe@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;
as well as URLs for NNTP newsgroup(s).