linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Yu Zhao <yuzhao@google.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Muchun Song <muchun.song@linux.dev>,
	David Hildenbrand <david@redhat.com>,
	Frank van der Linden <fvdl@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	Peter Xu <peterx@redhat.com>,
	Yang Shi <yang@os.amperecomputing.com>,
	linux-kernel@vger.kernel.org, ying.huang@intel.com,
	feng.tang@intel.com, fengwei.yin@intel.com,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [linux-next:master] [mm/hugetlb_vmemmap] 875fa64577: vm-scalability.throughput -34.3% regression
Date: Wed, 17 Jul 2024 09:52:51 +0200	[thread overview]
Message-ID: <3acefad9-96e5-4681-8014-827d6be71c7a@linux.ibm.com> (raw)
In-Reply-To: <202407091001.1250ad4a-oliver.sang@intel.com>

On 7/9/24 07:11, kernel test robot wrote:
> Hello,
> 
> kernel test robot noticed a -34.3% regression of vm-scalability.throughput on:
> 
> 
> commit: 875fa64577da9bc8e9963ee14fef8433f20653e7 ("mm/hugetlb_vmemmap: fix race with speculative PFN walkers")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> 
> [still regression on linux-next/master 0b58e108042b0ed28a71cd7edf5175999955b233]
>
This has hit s390 huge page backed KVM guests as well.
Our simple start/stop test case went from ~5 to over 50 seconds of runtime.


  parent reply	other threads:[~2024-07-17  7:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  5:11 [linux-next:master] [mm/hugetlb_vmemmap] 875fa64577: vm-scalability.throughput -34.3% regression kernel test robot
2024-07-10  6:22 ` Yu Zhao
2024-07-14 12:26   ` Oliver Sang
2024-07-15  2:40     ` Muchun Song
2024-07-15  4:08       ` Oliver Sang
2024-07-17  7:52 ` Janosch Frank [this message]
2024-07-17  7:59   ` Christian Borntraeger
2024-07-17  8:36   ` Yu Zhao
2024-07-17 15:44     ` Yu Zhao
2024-07-18  9:23       ` Marc Hartmayer
2024-07-19  8:42       ` Oliver Sang
2024-07-19 16:06         ` Yu Zhao
2024-08-03 22:07           ` Yu Zhao
2024-08-06  3:01             ` 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=3acefad9-96e5-4681-8014-827d6be71c7a@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=fvdl@google.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=muchun.song@linux.dev \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterx@redhat.com \
    --cc=willy@infradead.org \
    --cc=yang@os.amperecomputing.com \
    --cc=ying.huang@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).