From: Jakub Kicinski <kuba@kernel.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Vlastimil Babka <vbabka@suse.cz>,
Eric Dumazet <edumazet@google.com>,
Soheil Hassas Yeganeh <soheil@google.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: multi-memcg percpu charge cache
Date: Tue, 22 Apr 2025 18:10:22 -0700 [thread overview]
Message-ID: <20250422181022.308116c1@kernel.org> (raw)
In-Reply-To: <20250416180229.2902751-1-shakeel.butt@linux.dev>
On Wed, 16 Apr 2025 11:02:29 -0700 Shakeel Butt wrote:
> static void refill_stock(struct mem_cgroup *memcg, unsigned int nr_pages)
> {
> struct memcg_stock_pcp *stock;
> - unsigned int stock_pages;
> + struct mem_cgroup *cached;
> + uint8_t stock_pages;
Is it okay to use uintX_t now?
> unsigned long flags;
> + bool evict = true;
> + int i;
>
> VM_WARN_ON_ONCE(mem_cgroup_is_root(memcg));
>
> - if (!local_trylock_irqsave(&memcg_stock.stock_lock, flags)) {
> + if (nr_pages > MEMCG_CHARGE_BATCH ||
> + !local_trylock_irqsave(&memcg_stock.stock_lock, flags)) {
> /*
> - * In case of unlikely failure to lock percpu stock_lock
> - * uncharge memcg directly.
> + * In case of larger than batch refill or unlikely failure to
> + * lock the percpu stock_lock, uncharge memcg directly.
> */
We're bypassing the cache for > CHARGE_BATCH because the u8 math
may overflow? Could be useful to refocus the comment on the 'why'
> memcg_uncharge(memcg, nr_pages);
> return;
> }
nits notwithstanding:
Acked-by: Jakub Kicinski <kuba@kernel.org>
Thanks!
next prev parent reply other threads:[~2025-04-23 1:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 18:02 Shakeel Butt
2025-04-23 1:10 ` Jakub Kicinski [this message]
2025-04-23 22:16 ` Shakeel Butt
2025-04-23 22:30 ` Jakub Kicinski
2025-04-23 22:59 ` Shakeel Butt
2025-04-23 23:14 ` Shakeel Butt
2025-04-25 20:18 ` Shakeel Butt
2025-04-29 9:40 ` Hugh Dickins
2025-04-29 14:50 ` Shakeel Butt
2025-04-30 10:05 ` Vlastimil Babka
2025-04-30 15:16 ` Shakeel Butt
2025-04-29 12:13 ` Michal Hocko
2025-04-29 18:43 ` Shakeel Butt
2025-04-30 6:48 ` Michal Hocko
2025-04-30 9:57 ` Vlastimil Babka
2025-04-30 15:05 ` Shakeel Butt
2025-04-30 15:32 ` 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=20250422181022.308116c1@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=soheil@google.com \
--cc=vbabka@suse.cz \
/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