From: Shakeel Butt <shakeel.butt@linux.dev>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] memcg: drain obj stock on cpu hotplug teardown
Date: Tue, 11 Mar 2025 10:43:39 -0700 [thread overview]
Message-ID: <vr3bx3ahrdk53htnovmliyrr4byezgq6vaxdqpfe7mxj77xknv@qthti7keaqhv> (raw)
In-Reply-To: <Z9Bkn63LE4JRB3x7@google.com>
On Tue, Mar 11, 2025 at 04:28:15PM +0000, Roman Gushchin wrote:
[...]
> >
> > Anyways I wanted a simple fix for the backports and in parallel I am
> > working on cleaning up all the stock functions as I plan to add multi
> > memcg support.
>
> Really curious to see patches/more details here, I have some ideas here
> as well (nothing materialized yet though).
>
My eventual goal is to add support for multi memcg stock to solve the
charging cost of incoming networking traffic in multi-tenant
environment. In the cleanups my plan is to reduce the number of irq
disable operations in the most common paths and explore if for task
context we can do without any irq disabling operation (possibly by
separate stocks for in_task and !in_task contexts).
next prev parent reply other threads:[~2025-03-11 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 23:09 Shakeel Butt
2025-03-11 15:30 ` Johannes Weiner
2025-03-11 15:57 ` Shakeel Butt
2025-03-11 16:28 ` Roman Gushchin
2025-03-11 17:43 ` Shakeel Butt [this message]
2025-03-11 17:29 ` Johannes Weiner
2025-03-11 16:26 ` Roman Gushchin
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=vr3bx3ahrdk53htnovmliyrr4byezgq6vaxdqpfe7mxj77xknv@qthti7keaqhv \
--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=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=stable@vger.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