mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harry Yoo <harry@kernel.org>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
	 Christoph Lameter <cl@gentwo.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH] mm/percpu: clean up callers of pcpu_obj_full_size()
Date: Mon, 19 Oct 2026 18:49:26 +0100	[thread overview]
Message-ID: <atZWW7V0MI--HOke@thinkstation> (raw)
In-Reply-To: <20261019162803.281810-1-joshua.hahnjy@gmail.com>

On Mon, Oct 19, 2026 at 09:28:02AM -0700, Joshua Hahn wrote:
> The size of a pcpu allocation can be interpreted in two ways:
> 1. The size of the allocation attributable to a single CPU.
> 2. The total size of the allocation across all CPUs, including the
>    allocation overhead (for obj_cgroup membership).
> 
> In most accounting paths for percpu memory, we need the second
> definition (total size). Make this more obvious by coalescing the
> callers of pcpu_obj_full_size().
> 
> No functional changes intended.
> 
> Signed-off-by: Joshua Hahn <joshua.hahnjy@gmail.com>
> ---
>  mm/percpu.c | 39 +++++++++++++++++++--------------------
>  1 file changed, 19 insertions(+), 20 deletions(-)
> 
> diff --git a/mm/percpu.c b/mm/percpu.c
> index d7883507dc151..76848e096caee 100644
> --- a/mm/percpu.c
> +++ b/mm/percpu.c
> @@ -1623,7 +1623,7 @@ static bool pcpu_memcg_pre_alloc_hook(size_t size, gfp_t gfp,
>  	if (!objcg || obj_cgroup_is_root(objcg))
>  		return true;
>  
> -	if (obj_cgroup_charge(objcg, gfp, pcpu_obj_full_size(size)))
> +	if (obj_cgroup_charge(objcg, gfp, size))
>  		return false;
>  
>  	*objcgp = objcg;
> @@ -1642,11 +1642,10 @@ static void pcpu_memcg_post_alloc_hook(struct obj_cgroup *objcg,
>  		chunk->obj_exts[off >> PCPU_MIN_ALLOC_SHIFT].cgroup = objcg;
>  
>  		rcu_read_lock();
> -		mod_memcg_state(obj_cgroup_memcg(objcg), MEMCG_PERCPU_B,
> -				pcpu_obj_full_size(size));
> +		mod_memcg_state(obj_cgroup_memcg(objcg), MEMCG_PERCPU_B, size);
>  		rcu_read_unlock();
>  	} else {
> -		obj_cgroup_uncharge(objcg, pcpu_obj_full_size(size));
> +		obj_cgroup_uncharge(objcg, size);
>  	}
>  }
>  
> @@ -1662,11 +1661,10 @@ static void pcpu_memcg_free_hook(struct pcpu_chunk *chunk, int off, size_t size)

Perhaps it's better to rename 'size' parameter to 'full_size' in those
memcg hooks to make it clear it's expecting total size?

Otherwise LGTM!
Thanks for cleaning this up.

And it might be beyond the scope of this patch, but I think
trace_percpu_alloc_percpu_fail() should take full_size instead of size.

Wdyt?

-- 
Cheers,
Harry / Hyeonggon

  parent reply	other threads:[~2026-10-19 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 16:28 Joshua Hahn
2026-10-19 16:30 ` Joshua Hahn
2026-10-19 17:49 ` Harry Yoo [this message]
2026-10-19 18:16   ` Joshua Hahn
2026-10-19 18:49     ` Harry Yoo

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=atZWW7V0MI--HOke@thinkstation \
    --to=harry@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=dennis@kernel.org \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®