From: Qi Zheng <qi.zheng@linux.dev>
To: Shakeel Butt <shakeel.butt@linux.dev>,
kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Carlier" <devnexen@gmail.com>,
"Allen Pais" <apais@linux.microsoft.com>,
"Axel Rasmussen" <axelrasmussen@google.com>,
"Baoquan He" <bhe@redhat.com>,
"Chengming Zhou" <chengming.zhou@linux.dev>,
"Chen Ridong" <chenridong@huawei.com>,
"David Hildenbrand" <david@kernel.org>,
"Hamza Mahfooz" <hamzamahfooz@linux.microsoft.com>,
"Harry Yoo" <harry.yoo@oracle.com>,
"Hugh Dickins" <hughd@google.com>,
"Imran Khan" <imran.f.khan@oracle.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Kamalesh Babulal" <kamalesh.babulal@oracle.com>,
"Lance Yang" <lance.yang@linux.dev>,
"Liam Howlett" <Liam.Howlett@oracle.com>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Michal Hocko" <mhocko@suse.com>,
"Michal Koutný" <mkoutny@suse.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Muchun Song" <muchun.song@linux.dev>,
"Muchun Song" <songmuchun@bytedance.com>,
"Nhat Pham" <nphamcs@gmail.com>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Suren Baghdasaryan" <surenb@google.com>,
"Usama Arif" <usamaarif642@gmail.com>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Wei Xu" <weixugc@google.com>, "Yosry Ahmed" <yosry@kernel.org>,
"Yuanchu Xie" <yuanchu@google.com>, "Zi Yan" <ziy@nvidia.com>,
"Usama Arif" <usama.arif@linux.dev>,
cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [linus:master] [mm] 01b9da291c: stress-ng.switch.ops_per_sec 67.7% regression
Date: Wed, 13 May 2026 10:10:34 +0800 [thread overview]
Message-ID: <0e1b8994-944d-4dda-8966-3cd43661796d@linux.dev> (raw)
In-Reply-To: <agNO8G8tPnPuVrGq@linux.dev>
On 5/13/26 12:03 AM, Shakeel Butt wrote:
> On Tue, May 12, 2026 at 08:56:52PM +0800, kernel test robot wrote:
>>
>>
>> Hello,
>>
>> kernel test robot noticed a 67.7% regression of stress-ng.switch.ops_per_sec on:
>>
>>
>> commit: 01b9da291c4969354807b52956f4aae1f41b4924 ("mm: memcontrol: convert objcg to be per-memcg per-node type")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> This is most probably due to shuffling of struct mem_cgroup and struct
> mem_cgroup_per_node members.
Another possibility is that after objcg was split into per-node, the
slab accounting fast path is still designed assuming only one current
objcg per CPU:
struct obj_stock_pcp {
struct obj_cgroup *cached_objcg;
};
So it's may cause the following thrashing:
CPU stock cached = memcg/node0 objcg
free object tagged = memcg/node1 objcg
=> __refill_obj_stock --> objcg mismatch
=> drain_obj_stock()
=> cache switches to node1 objcg
next local allocation tagged = node0 objcg
=> mismatch again
=> drain_obj_stock()
>
> I will try to reproduce and will followup on this.
Thanks! I'll also try to reproduce it locally and work on a fix.
next prev parent reply other threads:[~2026-05-13 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:56 [linus:master] [mm] 01b9da291c: stress-ng.switch.ops_per_sec 67.7% regression kernel test robot
2026-05-12 16:03 ` Shakeel Butt
2026-05-13 2:10 ` Qi Zheng [this message]
2026-05-13 13:49 ` Shakeel Butt
2026-05-13 14:27 ` 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=0e1b8994-944d-4dda-8966-3cd43661796d@linux.dev \
--to=qi.zheng@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=apais@linux.microsoft.com \
--cc=axelrasmussen@google.com \
--cc=bhe@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=chenridong@huawei.com \
--cc=david@kernel.org \
--cc=devnexen@gmail.com \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=hughd@google.com \
--cc=imran.f.khan@oracle.com \
--cc=kamalesh.babulal@oracle.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=usamaarif642@gmail.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=yosry@kernel.org \
--cc=yuanchu@google.com \
--cc=ziy@nvidia.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