From: kernel test robot <oliver.sang@intel.com>
To: Dev Jain <dev.jain@arm.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Barry Song <baohua@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Pedro Falcato <pfalcato@suse.de>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Bang Li <libang.li@antgroup.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"bibo mao" <maobibo@loongson.cn>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>, Ingo Molnar <mingo@kernel.org>,
Jann Horn <jannh@google.com>, Lance Yang <ioworker0@gmail.com>,
Liam Howlett <liam.howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Peter Xu <peterx@redhat.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Yang Shi <yang@os.amperecomputing.com>, Zi Yan <ziy@nvidia.com>,
<linux-mm@kvack.org>, <oliver.sang@intel.com>
Subject: [linus:master] [mm] f822a9a81a: stress-ng.bigheap.realloc_calls_per_sec 37.3% regression
Date: Thu, 7 Aug 2025 16:17:09 +0800 [thread overview]
Message-ID: <202508071609.4e743d7c-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 37.3% regression of stress-ng.bigheap.realloc_calls_per_sec on:
commit: f822a9a81a31311d67f260aea96005540b18ab07 ("mm: optimize mremap() by PTE batching")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[still regression on linus/master 186f3edfdd41f2ae87fc40a9ccba52a3bf930994]
[still regression on linux-next/master b9ddaa95fd283bce7041550ddbbe7e764c477110]
testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-12
test machine: 192 threads 2 sockets Intel(R) Xeon(R) Platinum 8468V CPU @ 2.4GHz (Sapphire Rapids) with 384G memory
parameters:
nr_threads: 100%
testtime: 60s
test: bigheap
cpufreq_governor: performance
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202508071609.4e743d7c-lkp@intel.com
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250807/202508071609.4e743d7c-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-12/performance/x86_64-rhel-9.4/100%/debian-12-x86_64-20240206.cgz/igk-spr-2sp1/bigheap/stress-ng/60s
commit:
94dab12d86 ("mm: call pointers to ptes as ptep")
f822a9a81a ("mm: optimize mremap() by PTE batching")
94dab12d86cf77ff f822a9a81a31311d67f260aea96
---------------- ---------------------------
%stddev %change %stddev
\ | \
13777 ± 37% +45.0% 19979 ± 27% numa-vmstat.node1.nr_slab_reclaimable
367205 +2.3% 375703 vmstat.system.in
55106 ± 37% +45.1% 79971 ± 27% numa-meminfo.node1.KReclaimable
55106 ± 37% +45.1% 79971 ± 27% numa-meminfo.node1.SReclaimable
559381 -37.3% 350757 stress-ng.bigheap.realloc_calls_per_sec
11468 +1.2% 11603 stress-ng.time.system_time
296.25 +4.5% 309.70 stress-ng.time.user_time
0.81 ±187% -100.0% 0.00 perf-sched.sch_delay.avg.ms.__cond_resched.zap_pte_range.zap_pmd_range.isra.0
9.36 ±165% -100.0% 0.00 perf-sched.sch_delay.max.ms.__cond_resched.zap_pte_range.zap_pmd_range.isra.0
0.81 ±187% -100.0% 0.00 perf-sched.wait_time.avg.ms.__cond_resched.zap_pte_range.zap_pmd_range.isra.0
9.36 ±165% -100.0% 0.00 perf-sched.wait_time.max.ms.__cond_resched.zap_pte_range.zap_pmd_range.isra.0
5.50 ± 17% +390.9% 27.00 ± 56% perf-c2c.DRAM.local
388.50 ± 10% +114.7% 834.17 ± 33% perf-c2c.DRAM.remote
1214 ± 13% +107.3% 2517 ± 31% perf-c2c.HITM.local
135.00 ± 19% +130.9% 311.67 ± 32% perf-c2c.HITM.remote
1349 ± 13% +109.6% 2829 ± 31% perf-c2c.HITM.total
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-08-07 8:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 8:17 kernel test robot [this message]
2025-08-07 8:27 ` [linus:master] [mm] f822a9a81a: stress-ng.bigheap.realloc_calls_per_sec 37.3% regression Lorenzo Stoakes
2025-08-07 8:56 ` Dev Jain
2025-08-07 10:21 ` David Hildenbrand
2025-08-07 16:06 ` Dev Jain
2025-08-07 16:10 ` Lorenzo Stoakes
2025-08-07 16:16 ` Lorenzo Stoakes
2025-08-07 17:04 ` Dev Jain
2025-08-07 17:07 ` Lorenzo Stoakes
2025-08-07 17:11 ` Dev Jain
2025-08-07 17:37 ` Jann Horn
2025-08-07 17:41 ` Lorenzo Stoakes
2025-08-07 17:46 ` Jann Horn
2025-08-07 17:50 ` Dev Jain
2025-08-07 17:53 ` Lorenzo Stoakes
2025-08-07 17:51 ` Lorenzo Stoakes
2025-08-07 18:01 ` David Hildenbrand
2025-08-07 18:04 ` Lorenzo Stoakes
2025-08-07 18:13 ` David Hildenbrand
2025-08-07 18:07 ` Jann Horn
2025-08-07 18:31 ` David Hildenbrand
2025-08-07 19:52 ` Lorenzo Stoakes
2025-08-07 17:59 ` David Hildenbrand
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=202508071609.4e743d7c-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=libang.li@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=maobibo@loongson.cn \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=zhengqi.arch@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.