linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Muchun Song <muchun.song@linux.dev>, Zi Yan <ziy@nvidia.com>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH 3/5] mm: Remove references to folio in split_page_memcg()
Date: Thu, 13 Mar 2025 12:01:14 -0400	[thread overview]
Message-ID: <20250313160114.GD1252169@cmpxchg.org> (raw)
In-Reply-To: <20250313145856.4118428-4-willy@infradead.org>

On Thu, Mar 13, 2025 at 02:58:52PM +0000, Matthew Wilcox (Oracle) wrote:
> @@ -2697,6 +2697,23 @@ static int obj_cgroup_charge_pages(struct obj_cgroup *objcg, gfp_t gfp,
>  	return ret;
>  }
>  
> +static struct obj_cgroup *page_objcg(const struct page *first)

"first" is odd for that function. "page"?

> @@ -3091,16 +3107,16 @@ void __memcg_slab_free_hook(struct kmem_cache *s, struct slab *slab,
>   */
>  void split_page_memcg(struct page *first, unsigned order)
>  {
> -	struct folio *folio = page_folio(first);
> +	struct obj_cgroup *objcg = page_objcg(first);
>  	unsigned int i, nr = 1 << order;
>  
> -	if (mem_cgroup_disabled() || !folio_memcg_charged(folio))
> +	if (!objcg)
>  		return;

mem_cgroup_disabled() is a jump label, so a bit cheaper than the
branch. Can you keep that and do page_objcg() after it?

>  	for (i = 1; i < nr; i++)
> -		folio_page(folio, i)->memcg_data = folio->memcg_data;
> +		page_set_objcg(&first[i], objcg);
>  
> -	obj_cgroup_get_many(__folio_objcg(folio), nr - 1);
> +	obj_cgroup_get_many(objcg, nr - 1);
>  }

This is much nicer indeed. Thanks for doing this.

With the above nits considered,

Acked-by: Johannes Weiner <hannes@cmpxchg.org>


  reply	other threads:[~2025-03-13 16:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 14:58 [PATCH 0/5] Minor memcg cleanups & prep for memdescs Matthew Wilcox (Oracle)
2025-03-13 14:58 ` [PATCH 1/5] mm: Separate folio_split_memcg() from split_page_memcg() Matthew Wilcox (Oracle)
2025-03-13 15:52   ` Johannes Weiner
2025-03-13 17:07   ` Shakeel Butt
2025-03-13 17:22   ` Zi Yan
2025-03-13 14:58 ` [PATCH 2/5] mm: Simplify split_page_memcg() Matthew Wilcox (Oracle)
2025-03-13 15:54   ` Johannes Weiner
2025-03-13 17:08   ` Shakeel Butt
2025-03-13 17:23   ` Zi Yan
2025-03-13 14:58 ` [PATCH 3/5] mm: Remove references to folio in split_page_memcg() Matthew Wilcox (Oracle)
2025-03-13 16:01   ` Johannes Weiner [this message]
2025-03-13 16:05     ` Matthew Wilcox
2025-03-13 17:59     ` Matthew Wilcox
2025-03-13 18:03       ` Johannes Weiner
2025-03-13 17:10   ` Shakeel Butt
2025-03-13 14:58 ` [PATCH 4/5] mm: Simplify folio_memcg_charged() Matthew Wilcox (Oracle)
2025-03-13 16:03   ` Johannes Weiner
2025-03-13 16:15     ` Matthew Wilcox
2025-03-13 16:57       ` Shakeel Butt
2025-03-13 17:10   ` Shakeel Butt
2025-03-13 14:58 ` [PATCH 5/5] mm: Remove references to folio in __memcg_kmem_uncharge_page() Matthew Wilcox (Oracle)
2025-03-13 16:04   ` Johannes Weiner
2025-03-13 17:12   ` Shakeel Butt

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=20250313160114.GD1252169@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=willy@infradead.org \
    --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