linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Axel Rasmussen <axelrasmussen@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Revert "ptdesc: remove references to folios from __pagetable_ctor() and pagetable_dtor()"
Date: Wed, 25 Feb 2026 17:06:15 +0100	[thread overview]
Message-ID: <35c35f9f-244b-4591-a610-87606d5019f2@kernel.org> (raw)
In-Reply-To: <0d4f253f-6e92-4aec-9df1-e668b457d362@kernel.org>

On 2/25/26 17:04, David Hildenbrand (Arm) wrote:
> On 2/25/26 01:24, Axel Rasmussen wrote:
>> This change swapped out mod_node_page_state for lruvec_stat_add_folio.
>> But, these two APIs are not interchangeable: the lruvec version also
>> increments memcg stats, in addition to "global" pgdat stats.
>>
>> So after this change, the "pagetables" memcg stat in memory.stat always
>> yields "0", which is a userspace visible regression.
> 
> Argh, missed that these page tables are charged.
> 
>>
>> I tried to look for a refactor where we add a variant of
>> lruvec_stat_mod_folio which takes a pgdat and a memcg instead of a
>> folio, to try to adhere to the spirit of the original patch. But at the
>> end of the day this just means we have to call
>> folio_memcg(ptdesc_folio(ptdesc)) anyway, which doesn't really
>> accomplish much.
> 
> The goal of the original patch is obviously to get rid of any folio
> references in ptdesc code.
> 
> But if these ptdesc are charged, then we'd also need long-term a
> ptdesc->memcg_data.
> 
> For now we could still go through page->memcg_data, to avoid going
> through the folio.
> 
> But that requires some work, so likely we should just directly enlighten
> ptdesc to have memcg_data.
> 
> Agreed that, as a quick fix, reverting the commit might be best.
> 
> But let's wait a bit whether Willy has a comment.

Heh, Willy just replied while composing the mail. :)

-- 
Cheers,

David


  reply	other threads:[~2026-02-25 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  0:24 Axel Rasmussen
2026-02-25 16:03 ` Matthew Wilcox
2026-02-25 16:05   ` Matthew Wilcox
2026-02-25 16:08   ` David Hildenbrand (Arm)
2026-02-25 17:06     ` Shakeel Butt
2026-02-25 16:04 ` David Hildenbrand (Arm)
2026-02-25 16:06   ` David Hildenbrand (Arm) [this message]
2026-02-25 17:18 ` Shakeel Butt
2026-02-25 19:31 ` Johannes Weiner

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=35c35f9f-244b-4591-a610-87606d5019f2@kernel.org \
    --to=david@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    /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