From: Matthew Wilcox <willy@infradead.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, npache@redhat.com,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/huge_memory: consolidate order-related checks into folio_split_supported()
Date: Sat, 15 Nov 2025 05:07:45 +0000 [thread overview]
Message-ID: <aRgKoQT2ZYH_x2wa@casper.infradead.org> (raw)
In-Reply-To: <20251115025109.yerb7gbty4h7h63s@master>
On Sat, Nov 15, 2025 at 02:51:09AM +0000, Wei Yang wrote:
> I am not 100% for sure. While if we trust it returns 0 if folio doesn't
> support large folio, I am afraid we can trust it returns correct value it
> supports. Or that would be the issue to related file system.
>
> To be honest, I am lack of the capability to investigate all file system to
> make sure this value is properly setup.
Maybe you should just give up on this instead of asking so many
questions, misunderstanding the answers, and sending more patches full
of mistakes?
next prev parent reply other threads:[~2025-11-15 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 7:57 Wei Yang
2025-11-14 8:49 ` David Hildenbrand (Red Hat)
2025-11-14 12:43 ` Zi Yan
2025-11-14 14:30 ` Wei Yang
2025-11-14 20:53 ` Zi Yan
2025-11-15 2:42 ` Wei Yang
2025-11-14 15:03 ` Wei Yang
2025-11-14 19:36 ` David Hildenbrand (Red Hat)
2025-11-15 2:51 ` Wei Yang
2025-11-15 5:07 ` Matthew Wilcox [this message]
2025-11-15 9:43 ` Wei Yang
2025-12-04 15:13 ` Wei Yang
2025-11-19 12:37 ` Dan Carpenter
2025-11-19 12:39 ` Wei Yang
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=aRgKoQT2ZYH_x2wa@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.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