Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Usama Arif <usama.arif@linux.dev>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Shakeel Butt" <shakeel.butt@linux.dev>,
	"David Hildenbrand" <david@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	"Lorenzo Stoakes" <ljs@kernel.org>,
	"Michal Hocko" <mhocko@suse.com>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Mike Rapoport" <rppt@kernel.org>,
	"Roman Gushchin" <roman.gushchin@linux.dev>,
	"Suren Baghdasaryan" <surenb@google.com>,
	"Tejun Heo" <tj@kernel.org>,
	"Vlastimil Babka" <vbabka@kernel.org>,
	linux-mm@kvack.org, cgroups@vger.kernel.org, yi1.lai@intel.com
Subject: [linux-next:master] [mm/vmpressure]  ea928e9e18: stress-ng.mremap.ops_per_sec 36.2% regression
Date: Thu, 13 Aug 2026 21:16:22 +0800	[thread overview]
Message-ID: <202608131743.c6a7dda4-lkp@intel.com> (raw)



Hello,

kernel test robot noticed a 36.2% regression of stress-ng.mremap.ops_per_sec on:

commit: ea928e9e18da682e9a5bc40aa862bff7ce5ae42e ("mm/vmpressure: move v1 userspace eventfd code into memcontrol-v1.c") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

in testcase: stress-ng
version: stress-ng-x86_64-29ce10a2c-1_20260712
with following parameters:

	nr_threads: 100%
	testtime: 60s
	test: mremap
	cpufreq_governor: performance



config: x86_64-rhel-9.4 (CONFIG_MEMCG=y and CONFIG_MEMCG_V1 is not set)
compiler: gcc-14
test machine: 256 threads 4 sockets INTEL(R) XEON(R) PLATINUM 8592+ (Emerald Rapids) with 256G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)




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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202608131743.c6a7dda4-lkp@intel.com


2026-08-11 09:13:23 sysctl -w kernel.sched_autogroup_enabled=0 kernel.sched_autogroup_enabled = 0
2026-08-11 09:13:23 stress-ng --timeout 60 --times --verify --metrics --no-rand-seed --mremap 256
stress-ng: info:  [10886] setting to a 1 min run per stressor
stress-ng: info:  [10886] dispatching hogs: 256 mremap
stress-ng: info:  [11033] mremap: using 1MB per stressor instance (total 256MB of 243.06GB available memory)
stress-ng: metrc: [10886] stressor       bogo ops real time  usr time  sys time   bogo ops/s     bogo ops/s CPU used per       RSS Max
stress-ng: metrc: [10886]                           (secs)    (secs)    (secs)   (real time) (usr+sys time) instance (%)          (KB)
stress-ng: metrc: [10886] mremap          2212529     59.96    209.34  15014.92     36901.22         145.33        99.19          6684
stress-ng: metrc: [10886] miscellaneous metrics:
stress-ng: metrc: [10886] mremap            151372.07 nanosecs per mremap call (harmonic mean of 256 instances)
stress-ng: info:  [10886] for a 60.01s run time:
stress-ng: info:  [10886]   15363.58s available CPU time
stress-ng: info:  [10886]     209.34s user time   (  1.36%)
stress-ng: info:  [10886]   15015.19s system time ( 97.73%)
stress-ng: info:  [10886]   15224.53s total time  ( 99.09%)
stress-ng: info:  [10886] load average: 163.54 47.28 16.30
stress-ng: info:  [10886] skipped: 0
stress-ng: info:  [10886] passed: 256: mremap (256)
stress-ng: info:  [10886] failed: 0
stress-ng: info:  [10886] metrics untrustworthy: 0
stress-ng: info:  [10886] successful run completed in 1 min



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260813/202608131743.c6a7dda4-lkp@intel.com



--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




                 reply	other threads:[~2026-08-13 13:16 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=202608131743.c6a7dda4-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=liam@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=lkp@intel.com \
    --cc=mhocko@suse.com \
    --cc=mkoutny@suse.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=tj@kernel.org \
    --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