From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
Waiman Long <llong@redhat.com>, Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: decouple memcg_hotplug_cpu_dead from stock_lock
Date: Mon, 14 Apr 2025 10:52:22 -0700 [thread overview]
Message-ID: <atnweqyv7rnyzei3at2dm4xxca4ctvuod2w7brejg4b5zydgdm@xobzurjmjhy5> (raw)
In-Reply-To: <20250410220618.405d00875ca61043c4ffa6e1@linux-foundation.org>
(I was trying to reply last week but my email stopped working, so trying
again)
On Thu, Apr 10, 2025 at 10:06:18PM -0700, Andrew Morton wrote:
> On Thu, 10 Apr 2025 14:06:23 -0700 Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> > The function memcg_hotplug_cpu_dead works on the stock of a remote dead
> > CPU and drain_obj_stock works on the given stock instead of local stock,
> > so there is no need to take local stock_lock anymore.
> >
> > @@ -1964,10 +1964,10 @@ static int memcg_hotplug_cpu_dead(unsigned int cpu)
> >
> > stock = &per_cpu(memcg_stock, cpu);
> >
> > - /* drain_obj_stock requires stock_lock */
> > - local_lock_irqsave(&memcg_stock.stock_lock, flags);
> > - drain_obj_stock(stock);
> > - local_unlock_irqrestore(&memcg_stock.stock_lock, flags);
> > + local_irq_save(flag);
> > + /* stock of a remote dead cpu, no need for stock_lock. */
> > + __drain_obj_stock(stock);
> > + local_irq_restore(flag);
> >
>
> s/flag/flags/
>
> Obviously what-i-got isn't what-you-tested. Please check what happened
> here,
Sorry about that. I tested the previous version where I had
drain_obj_stock() as a separate function but after seeing that there is
just one caller, I manually inlined it but forgot to test before
sending.
next prev parent reply other threads:[~2025-04-14 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 21:06 Shakeel Butt
2025-04-11 0:00 ` Roman Gushchin
2025-04-11 5:06 ` Andrew Morton
2025-04-14 17:52 ` Shakeel Butt [this message]
2025-04-11 8:55 ` Vlastimil Babka
2025-04-11 14:06 ` Sebastian Andrzej Siewior
2025-04-11 17:54 ` Shakeel Butt
2025-04-11 18:06 ` Vlastimil Babka
2025-04-11 18:12 ` Shakeel Butt
2025-04-14 17:55 ` Shakeel Butt
2025-04-15 6:30 ` Sebastian Andrzej Siewior
2025-04-15 17:01 ` 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=atnweqyv7rnyzei3at2dm4xxca4ctvuod2w7brejg4b5zydgdm@xobzurjmjhy5 \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llong@redhat.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=yosry.ahmed@linux.dev \
/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