From: Hao Li <hao.li@linux.dev>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: Vlastimil Babka <vbabka@suse.cz>, Hao Li <haolee.swjtu@gmail.com>,
akpm@linux-foundation.org, harry.yoo@oracle.com, cl@gentwo.org,
rientjes@google.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tim.c.chen@intel.com, yu.c.chen@intel.com
Subject: Re: [PATCH v2] slub: keep empty main sheaf as spare in __pcs_replace_empty_main()
Date: Fri, 16 Jan 2026 17:09:31 +0800 [thread overview]
Message-ID: <n3xsvtgidf65f62x3mwgcoxnglflzozxpxjhtvawmvoljo3t6o@kahjwxud5aqf> (raw)
In-Reply-To: <aWoB0/RxDZeK6LU0@intel.com>
On Fri, Jan 16, 2026 at 05:16:03PM +0800, Zhao Liu wrote:
> > I'd like to dig a bit deeper to confirm whether the "256 tasks" result is truly
> > a regression.
>
> The "256" seems align closely with the NUMA topology on my machine, so
> I'm unsure how it will perform on other machines.
Got it. Thanks, in any case, I'll try to reproduce it first.
>
> > Could you please share the original full report, or let me know
> > which test case under will-it-scale/ you used?
>
> I mainly followed Suneeth's steps [*]:
>
> 1) git clone https://github.com/antonblanchard/will-it-scale.git
> 2) git clone https://github.com/intel/lkp-tests.git
> 3) cd will-it-scale && git apply
> lkp-tests/programs/will-it-scale/pkg/will-it-scale.patch
> 4) make
> 5) python3 runtest.py mmap2 25 process 0 0 1 8 64 128 192 256
>
> [*]: https://lore.kernel.org/all/262c742f-dc0c-4adc-b23c-047cd3298a5e@amd.com/
Thanks!
>
> Sine the raw perf.data files are too big to be blocked, if you need to
> see any specific part of the content, I can paste the info for you.
>
> Regards,
> Zhao
>
next prev parent reply other threads:[~2026-01-16 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 0:26 Hao Li
2025-12-15 14:30 ` Vlastimil Babka
2025-12-16 2:34 ` Hao Lee
2025-12-22 10:20 ` Harry Yoo
2026-01-05 15:58 ` Vlastimil Babka
2026-01-15 10:12 ` Zhao Liu
2026-01-15 16:19 ` Vlastimil Babka
2026-01-16 9:07 ` Zhao Liu
2026-01-16 9:11 ` Hao Li
2026-01-16 4:06 ` Hao Li
2026-01-16 9:16 ` Zhao Liu
2026-01-16 9:09 ` Hao Li [this message]
2026-01-19 6:07 ` Hao Li
2026-01-20 8:21 ` Zhao Liu
2026-01-21 3:15 ` Hao Li
2026-01-21 13:17 ` Zhao Liu
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=n3xsvtgidf65f62x3mwgcoxnglflzozxpxjhtvawmvoljo3t6o@kahjwxud5aqf \
--to=hao.li@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=haolee.swjtu@gmail.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=tim.c.chen@intel.com \
--cc=vbabka@suse.cz \
--cc=yu.c.chen@intel.com \
--cc=zhao1.liu@intel.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