From: Roman Gushchin <roman.gushchin@linux.dev>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: hannes@cmpxchg.org, hughd@google.com, mhocko@suse.com,
shakeel.butt@linux.dev, muchun.song@linux.dev,
david@redhat.com, lorenzo.stoakes@oracle.com, ziy@nvidia.com,
harry.yoo@oracle.com, baolin.wang@linux.alibaba.com,
Liam.Howlett@oracle.com, npache@redhat.com,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH v2 1/4] mm: thp: replace folio_memcg() with folio_memcg_charged()
Date: Wed, 24 Sep 2025 09:10:07 +0000 [thread overview]
Message-ID: <7ia4plbg6wsw.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <0ac716fb7fea89ada92ad544f88ca546e43d1f29.1758618527.git.zhengqi.arch@bytedance.com> (Qi Zheng's message of "Tue, 23 Sep 2025 17:16:22 +0800")
Qi Zheng <zhengqi.arch@bytedance.com> writes:
> From: Muchun Song <songmuchun@bytedance.com>
>
> folio_memcg_charged() is intended for use when the user is unconcerned
> about the returned memcg pointer. It is more efficient than folio_memcg().
> Therefore, replace folio_memcg() with folio_memcg_charged().
>
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Acked-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev>
next prev parent reply other threads:[~2025-09-24 9:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 9:16 [PATCH v2 0/4] reparent the THP split queue Qi Zheng
2025-09-23 9:16 ` [PATCH v2 1/4] mm: thp: replace folio_memcg() with folio_memcg_charged() Qi Zheng
2025-09-24 9:10 ` Roman Gushchin [this message]
2025-09-23 9:16 ` [PATCH v2 2/4] mm: thp: introduce folio_split_queue_lock and its variants Qi Zheng
2025-09-23 9:16 ` [PATCH v2 3/4] mm: thp: use folio_batch to handle THP splitting in deferred_split_scan() Qi Zheng
2025-09-23 15:31 ` Zi Yan
2025-09-24 9:57 ` Qi Zheng
2025-09-24 14:57 ` Zi Yan
2025-09-24 12:31 ` David Hildenbrand
2025-09-23 9:16 ` [PATCH v2 4/4] mm: thp: reparent the split queue during memcg offline Qi Zheng
2025-09-23 15:44 ` Zi Yan
2025-09-24 9:58 ` Qi Zheng
2025-09-24 9:23 ` Roman Gushchin
2025-09-24 10:06 ` Qi Zheng
2025-09-24 12:38 ` David Hildenbrand
2025-09-25 6:11 ` Qi Zheng
2025-09-25 19:35 ` David Hildenbrand
2025-09-25 19:49 ` Zi Yan
2025-09-25 22:15 ` Shakeel Butt
2025-09-25 22:35 ` Shakeel Butt
2025-09-26 6:57 ` Qi Zheng
2025-09-26 16:36 ` Shakeel Butt
2025-09-24 13:49 ` kernel test robot
2025-09-24 14:22 ` Harry Yoo
2025-09-25 6:29 ` Qi Zheng
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=7ia4plbg6wsw.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=cgroups@vger.kernel.org \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=hughd@google.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=zhengqi.arch@bytedance.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