mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ye Liu <ye.liu@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ye Liu <liuye@kylinos.cn>, "Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Kairui Song <kasong@tencent.com>,
	Qi Zheng <qi.zheng@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Barry Song <baohua@kernel.org>,
	Axel Rasmussen <axelrasmussen@google.com>,
	Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
	Zi Yan <ziy@nvidia.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Nico Pache <npache@redhat.com>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Lance Yang <lance.yang@linux.dev>,
	Usama Arif <usama.arif@linux.dev>,
	driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] mm/thp: expose deferred split folio memory usage in meminfo
Date: Mon, 20 Jul 2026 10:36:14 +0800	[thread overview]
Message-ID: <c0265ec9-e983-4547-a166-7c1d30237b73@linux.dev> (raw)
In-Reply-To: <b6b04cf2-30d0-4511-9bd4-042b176c1b31@kernel.org>



在 2026/7/17 18:29, David Hildenbrand (Arm) 写道:
> On 7/17/26 11:54, Ye Liu wrote:
>>
>>
>> 在 2026/7/17 17:48, Lorenzo Stoakes (ARM) 写道:
>>> On Fri, Jul 17, 2026 at 11:33:05AM +0200, David Hildenbrand (Arm) wrote:
>>>>
>>>> Don't expose it to user space.
>>>
>>> Yeah please stop.
>>>
>>> We don't want this change, it exposes internal implementation details. It's a
>>> no.
>>>
>>> Next time send an RFC or a discussion thread.
>>>
>> Yes, sending an RFC would be more appropriate.                                                  
>>                                                                                                 
>> I'd also like to ask if it's possible to implement this in                                      
>> `/sys/kernel/debug/deferred_split_pages`, or are you completely against querying this statistic?
> 
> It's not pages. It's folios.
> 
> You don't know how much memory is there to reclaim. You don't know if it can
> even be reclaimed.
> 
> You don't even know if there can be any memory reclaimed *at all*, because there
> are scenarios where we add folios that are actually *not* partially mapped today.
> 
> You don't even know the relationship to memcgs.
> 
>>                                                                                                 
>> How can we quickly identify this situation?                                                     
>> I believe some people will still be confused: where did the memory go?                          
> 
> Just like other caches that are shrunk on memory pressure.
> 
> We do have a "split_deferred" and a "nr_anon_partially_mapped" counter in
> "/sys/kernel/mm/transparent_hugepage/hugepages-2048kB/", maybe that helps.
> 
Thank you, it really helped.

-- 
Thanks,
Ye Liu


  reply	other threads:[~2026-07-20  2:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  6:30 Ye Liu
2026-07-17  8:08 ` Lorenzo Stoakes (ARM)
2026-07-17  9:24   ` Ye Liu
2026-07-17  9:38     ` liuye
2026-07-17  9:47       ` Lorenzo Stoakes (ARM)
2026-07-17 10:29       ` Johannes Weiner
2026-07-20  2:31         ` Ye Liu
2026-07-17  8:37 ` David Hildenbrand (Arm)
2026-07-17  8:47   ` Lorenzo Stoakes (ARM)
2026-07-17  9:31   ` Ye Liu
2026-07-17  9:33     ` David Hildenbrand (Arm)
2026-07-17  9:48       ` Lorenzo Stoakes (ARM)
2026-07-17  9:54         ` Ye Liu
2026-07-17 10:29           ` David Hildenbrand (Arm)
2026-07-20  2:36             ` Ye Liu [this message]
2026-07-17 10:29     ` Vlastimil Babka (SUSE)

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=c0265ec9-e983-4547-a166-7c1d30237b73@linux.dev \
    --to=ye.liu@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=dakr@kernel.org \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=kasong@tencent.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=npache@redhat.com \
    --cc=qi.zheng@linux.dev \
    --cc=rafael@kernel.org \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=weixugc@google.com \
    --cc=yuanchu@google.com \
    --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

Powered by JetHome