From: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
To: linux-mm@kvack.org
Cc: "Roman Gushchin" <roman.gushchin@linux.dev>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Shakeel Butt" <shakeel.butt@linux.dev>,
"Andrew Morton" <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
"Tejun Heo" <tj@kernel.org>, "Michal Koutný" <mkoutny@suse.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Muchun Song" <muchun.song@linux.dev>,
"Allen Pais" <apais@linux.microsoft.com>,
"Yosry Ahmed" <yosryahmed@google.com>
Subject: Re: A path forward to cleaning up dying cgroups?
Date: Wed, 5 Feb 2025 12:50:19 -0500 [thread overview]
Message-ID: <ccd67fd2-268a-4e83-9491-e401fa57229c@linux.microsoft.com> (raw)
In-Reply-To: <Z6OkXXYDorPrBvEQ@hm-sls2>
Cc: Shakeel Butt <shakeel.butt@linux.dev>
On 2/5/25 12:48, Hamza Mahfooz wrote:
> I was just curious as to what the status of the issue described in [1]
> is. It appears that the last time someone took a stab at it was in [2].
>
> Though it seems like there has been relative silence regarding it since
> then. So, has there been any discussion regarding the issue since then
> and does anyone know if there is consensus on how we should go about
> resolving this issue within the kernel?
>
> BR,
> Hamza
>
> [1] https://lwn.net/Articles/895431/
> [2] https://lore.kernel.org/r/20220621125658.64935-1-songmuchun@bytedance.com/
next prev parent reply other threads:[~2025-02-05 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 17:48 Hamza Mahfooz
2025-02-05 17:50 ` Hamza Mahfooz [this message]
2025-02-05 18:08 ` Johannes Weiner
2025-02-05 18:16 ` Yosry Ahmed
2025-02-06 4:56 ` Kairui Song
2025-02-05 18:31 ` Roman Gushchin
2025-02-05 18:46 ` Shakeel Butt
2025-02-06 3:30 ` Muchun Song
2025-02-06 3:34 ` Waiman Long
2025-02-06 15:51 ` Kamalesh Babulal
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=ccd67fd2-268a-4e83-9491-e401fa57229c@linux.microsoft.com \
--to=hamzamahfooz@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=apais@linux.microsoft.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.org \
--cc=yosryahmed@google.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