From: kernel test robot <yi1.lai@intel.com>
To: Barry Song <baohua@kernel.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Kairui Song <kasong@tencent.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Baoquan He <baoquan.he@linux.dev>, Chris Li <chrisl@kernel.org>,
Kemeng Shi <shikemeng@huaweicloud.com>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>, Nhat Pham <nphamcs@gmail.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
Usama Arif <usama.arif@linux.dev>,
linux-mm@kvack.org, yi1.lai@intel.com
Subject: [linus:master] [mm] 8d596d8b81: stress-ng.mlockmany.ops_per_sec 10.5% improvement
Date: Mon, 19 Oct 2026 09:32:33 +0800 [thread overview]
Message-ID: <202610190949.71c20bb5-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 10.5% improvement of stress-ng.mlockmany.ops_per_sec on:
commit: 8d596d8b81ef56bf61538d6b4761a7b0d6138280 ("mm: avoid unnecessary lru drain for wp_can_reuse_anon_folio()") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 256 threads 4 sockets INTEL(R) XEON(R) PLATINUM 8592+ (Emerald Rapids) with 256G memory
parameters:
nr_threads: 100%
testtime: 60s
test: mlockmany
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261019/202610190949.71c20bb5-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-14/performance/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-emr-2sp1/mlockmany/stress-ng/60s
commit:
819bfbd47e ("mm/page_alloc: remove set_page_private() in prep_compound_tail()")
8d596d8b81 ("mm: avoid unnecessary lru drain for wp_can_reuse_anon_folio()")
819bfbd47e49df89 8d596d8b81ef56bf61538d6b476
---------------- ---------------------------
%stddev %change %stddev
\ | \
1050118 +10.6% 1161061 ± 2% stress-ng.mlockmany.ops
17541 +10.5% 19384 ± 2% stress-ng.mlockmany.ops_per_sec
2933233 -7.5% 2714192 stress-ng.time.involuntary_context_switches
76.26 +29.3% 98.61 ± 3% stress-ng.time.user_time
2425877 +9.4% 2654908 ± 2% stress-ng.time.voluntary_context_switches
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
reply other threads:[~2026-10-19 1:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610190949.71c20bb5-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=kasong@tencent.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
/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
all inboxes | Powered by JetHome®