mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: kernel test robot <yi1.lai@intel.com>, Lorenzo Stoakes <ljs@kernel.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Daehyeon Ko <4ncienth@gmail.com>, Mike Rapoport <rppt@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Hagen Paul Pfeifer <hagen@jauu.net>,
	Jakub Kacinski <kuba@kernel.org>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	Michal Hocko <mhocko@suse.com>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Suren Baghdasaryan <surenb@google.com>,
	linux-mm@kvack.org
Subject: Re: [linus:master] [mm/secretmem] 97d34aa65c: stress-ng.secretmem.ops_per_sec 99.5% regression
Date: Wed, 23 Sep 2026 08:35:47 +0200	[thread overview]
Message-ID: <7ea6e90a-e2fb-4793-b6ea-e292388bdfdf@kernel.org> (raw)
In-Reply-To: <202609230824.7a9189aa-lkp@intel.com>

On 9/23/26 03:00, kernel test robot wrote:
> 
> 
> Hello,
> 
> kernel test robot noticed a 99.5% regression of stress-ng.secretmem.ops_per_sec on:
> 
> commit: 97d34aa65c29cca85e3e9050f4c936389b38a054 ("mm/secretmem: properly account locked pages") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

Well maybe there is some inefficiency that can be fixed (haven't checked)
but if it's the cost for proper accounting then so be it? I doubt creating
secretmem pages is something userspace would have to do intensively enough
to matter.

> testcase: stress-ng
> config: x86_64-rhel-9.4
> compiler: gcc-14
> test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G memory
> parameters:
> 
> 	nr_threads: 100%
> 	testtime: 60s
> 	test: secretmem
> 	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 <yi1.lai@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202609230824.7a9189aa-lkp@intel.com
> 
> 
> Details are as below:
> -------------------------------------------------------------------------------------------------->
> 
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20260923/202609230824.7a9189aa-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-spr-r02/secretmem/stress-ng/60s
> 
> commit: 
>   35b0fb391b ("mm/mremap: reset unfaulted VMA page offset for MREMAP_DONTUNMAP")
>   97d34aa65c ("mm/secretmem: properly account locked pages")
> 
> 35b0fb391b0df573 97d34aa65c29cca85e3e9050f4c
> ---------------- --------------------------- 
>          %stddev     %change         %stddev
>              \          |                \  
>    6080503           -99.6%      23092 ±  3%  stress-ng.secretmem.ops
>      85584           -99.5%     385.28 ±  3%  stress-ng.secretmem.ops_per_sec
>      71.48           -16.0%      60.07        stress-ng.time.elapsed_time
>      71.48           -16.0%      60.07        stress-ng.time.elapsed_time.max
>      97435 ±  2%   +1276.4%    1341103        stress-ng.time.involuntary_context_switches
>     230308           -96.1%       9096        stress-ng.time.maximum_resident_set_size
>   18401243         +3349.6%  6.348e+08        stress-ng.time.minor_page_faults
>      20417            -8.7%      18639        stress-ng.time.percent_of_cpu_this_job_got
>      14581           -25.0%      10937        stress-ng.time.system_time
>      13.34         +1858.5%     261.33        stress-ng.time.user_time
>       6898 ±  2%  +96037.7%    6631576 ±  3%  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.
> 
> 


  reply	other threads:[~2026-09-23  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  1:00 kernel test robot
2026-09-23  6:35 ` Vlastimil Babka (SUSE) [this message]
2026-09-23  7:19   ` Lorenzo Stoakes (ARM)

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=7ea6e90a-e2fb-4793-b6ea-e292388bdfdf@kernel.org \
    --to=vbabka@kernel.org \
    --cc=4ncienth@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=hagen@jauu.net \
    --cc=hawk@kernel.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --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=oe-lkp@lists.linux.dev \
    --cc=rppt@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=surenb@google.com \
    --cc=yi1.lai@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

all inboxes | Powered by JetHome®