From: David Hildenbrand <david@redhat.com>
To: kernel test robot <oliver.sang@intel.com>,
Yin Fengwei <fengwei.yin@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Yu Zhao <yuzhao@google.com>, Ryan Roberts <ryan.roberts@arm.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Matthew Wilcox <willy@infradead.org>,
Minchan Kim <minchan@kernel.org>,
Vishal Moola <vishal.moola@gmail.com>,
Yang Shi <shy828301@gmail.com>,
linux-mm@kvack.org
Subject: Re: [linus:master] [madvise] 2f406263e3: stress-ng.mremap.ops_per_sec 6.7% regression
Date: Fri, 29 Nov 2024 10:45:51 +0100 [thread overview]
Message-ID: <e08c88bf-8aa0-4b18-9d8a-77f1a60436e7@redhat.com> (raw)
In-Reply-To: <202411291513.ad55672a-lkp@intel.com>
On 29.11.24 08:49, kernel test robot 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
A MADV_COLD / MADV_PAGEOUT patch for large folios / THP affecting a
stress-ng mremap test (where propably no THP are used)?
Sounds unlikely ... ;)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-11-29 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 7:49 kernel test robot
2024-11-29 9:45 ` David Hildenbrand [this message]
2024-12-02 22:24 ` Yu Zhao
2024-12-05 8:25 ` Oliver Sang
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=e08c88bf-8aa0-4b18-9d8a-77f1a60436e7@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=minchan@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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