Re: [linus:master] [madvise] 2f406263e3: stress-ng.mremap.ops_per_sec 6.7% regression

[Yu Zhao <yuzhao@google.com>]

Hi Oliver,

On Fri, Nov 29, 2024 at 12:50 AM kernel test robot
<oliver.sang@intel.com> wrote:
>
>
>
> Hello,
>
> kernel test robot noticed a 6.7% regression of stress-ng.mremap.ops_per_sec on:
>
>
> commit: 2f406263e3e954aa24c1248edcfa9be0c1bb30fa ("madvise:madvise_cold_or_pageout_pte_range(): don't use mapcount() against large folio for sharing check")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [still regression on fix commit cc864ebba5f612ce2960e7e09322a193e8fda0d7]
>
> testcase: stress-ng
> config: x86_64-rhel-8.3
> compiler: gcc-12
> test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G memory
> parameters:
>
>         nr_threads: 100%
>         testtime: 60s
>         test: mremap
>         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/202411291513.ad55672a-lkp@intel.com
>
>
> Details are as below:
> -------------------------------------------------------------------------------------------------->
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20241129/202411291513.ad55672a-lkp@intel.com
>
> =========================================================================================
> compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
>   gcc-12/performance/x86_64-rhel-8.3/100%/debian-12-x86_64-20240206.cgz/lkp-icl-2sp7/mremap/stress-ng/60s
>
> commit:
>   6867c7a332 ("mm: multi-gen LRU: don't spin during memcg release")
>   2f406263e3 ("madvise:madvise_cold_or_pageout_pte_range(): don't use mapcount() against large folio for sharing check")

The .config you attached shows CONFIG_LRU_GEN_ENABLED is NOT set for
LKP. So this regression can't be from the first commit above.

Also, I asked you a few times if it's possible to set it to 'y'. It'd
be great if we could do that :)