From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Harry Yoo <harry@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Qi Zheng <qi.zheng@linux.dev>, Alexandre Ghiti <alex@ghiti.fr>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Meta kernel team <kernel-team@meta.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH v3] memcg: cache obj_stock by memcg, not by objcg pointer
Date: Fri, 22 May 2026 09:16:09 -0700 [thread overview]
Message-ID: <ahB_kaWXowIIQ6dQ@linux.dev> (raw)
In-Reply-To: <20260519134927.ee04379d07b0674872422c06@linux-foundation.org>
On Tue, May 19, 2026 at 01:49:27PM -0700, Andrew Morton wrote:
> On Tue, 19 May 2026 13:11:13 -0700 Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> > Andrew, please don't send this patch to Linus until we decide on the option.
>
> No probs, I added a note-to-self.
Here is my suggestion on how to proceed.
1. Let's drop this patch (memcg: cache obj_stock by memcg, not by objcg pointer)
from mm-tree.
2. Let's not add anything to 7.1.
3. 7.2+ will have the multi-objcg series [1] and the patches will have fixes
tag. If someone uses non-LTS 7.1, they can easily find those patches and can
backport them.
Please let me know if there are any concerns.
[1] https://lore.kernel.org/20260522011908.1669332-1-shakeel.butt@linux.dev/
next prev parent reply other threads:[~2026-05-22 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 22:28 [PATCH v3] memcg: cache obj_stock by memcg, not by objcg pointer Shakeel Butt
2026-05-18 23:41 ` Shakeel Butt
2026-05-19 3:35 ` Qi Zheng
2026-05-19 6:46 ` Harry Yoo
2026-05-19 14:02 ` Shakeel Butt
2026-05-19 15:00 ` Harry Yoo
2026-05-19 20:11 ` Shakeel Butt
2026-05-19 20:49 ` Andrew Morton
2026-05-22 16:16 ` Shakeel Butt [this message]
2026-05-19 23:39 ` 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=ahB_kaWXowIIQ6dQ@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=joshua.hahnjy@gmail.com \
--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=oliver.sang@intel.com \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@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