linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: David Hildenbrand <david@redhat.com>,
	kernel test robot <oliver.sang@intel.com>,
	Peter Xu <peterx@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Matthew Wilcox <willy@infradead.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	WANG Xuerui <kernel@xen0n.name>, <linux-mm@kvack.org>,
	<ying.huang@intel.com>, <feng.tang@intel.com>
Subject: Re: [linus:master] [mm] c0bff412e6: stress-ng.clone.ops_per_sec -2.9% regression
Date: Thu, 1 Aug 2024 14:39:12 +0800	[thread overview]
Message-ID: <439265d8-e71e-41db-8a46-55366fdd334e@intel.com> (raw)
In-Reply-To: <193e302c-4401-4756-a552-9f1e07ecedcf@redhat.com>

Hi David,

On 7/30/2024 4:11 PM, David Hildenbrand wrote:
> On 30.07.24 07:00, kernel test robot wrote:
>>
>>
>> Hello,
>>
>> kernel test robot noticed a -2.9% regression of 
>> stress-ng.clone.ops_per_sec on:
> 
> Is that test even using hugetlb? Anyhow, this pretty much sounds like 
> noise and can be ignored.
> 
It's not about hugetlb. It looks like related with the change:

diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index 888353c209c03..7577fe7debafc 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -1095,7 +1095,12 @@ PAGEFLAG(Isolated, isolated, PF_ANY);
  static __always_inline int PageAnonExclusive(const struct page *page)
  {
         VM_BUG_ON_PGFLAGS(!PageAnon(page), page);
-       VM_BUG_ON_PGFLAGS(PageHuge(page) && !PageHead(page), page);
+       /*
+        * HugeTLB stores this information on the head page; THP keeps 
it per
+        * page
+        */
+       if (PageHuge(page))
+               page = compound_head(page);
         return test_bit(PG_anon_exclusive, &PF_ANY(page, 1)->flags);


The PageAnonExclusive() function is changed. And the profiling data
showed it:

       0.00            +3.9        3.90 
perf-profile.calltrace.cycles-pp.folio_try_dup_anon_rmap_ptes.copy_present_ptes.copy_pte_range.copy_p4d_range.copy_page_range

According 
https://download.01.org/0day-ci/archive/20240730/202407301049.5051dc19-oliver.sang@intel.com/config-6.9.0-rc4-00197-gc0bff412e67b:
	# CONFIG_DEBUG_VM is not set
So maybe such code change could bring difference?

And yes. 2.9% regression can be in noise range. Thanks.


Regards
Yin, Fengwei


  reply	other threads:[~2024-08-01  6:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  5:00 [linus:master] [mm] c0bff412e6: stress-ng.clone.ops_per_sec -2.9% regression kernel test robot
2024-07-30  8:11 ` David Hildenbrand
2024-08-01  6:39   ` Yin, Fengwei [this message]
2024-08-01  6:49     ` David Hildenbrand
2024-08-01  7:44       ` Yin, Fengwei
2024-08-01  7:54         ` David Hildenbrand
2024-08-01 13:30       ` Mateusz Guzik
2024-08-01 13:34         ` David Hildenbrand
2024-08-01 13:37           ` Mateusz Guzik
2024-08-01 13:44             ` David Hildenbrand
2024-08-12  4:43               ` Yin Fengwei
2024-08-12  4:49                 ` Mateusz Guzik
2024-08-12  8:12                   ` David Hildenbrand
2024-08-12  8:18                     ` Mateusz Guzik
2024-08-12  8:23                       ` David Hildenbrand
2024-08-13  7:09                   ` Yin Fengwei
2024-08-13  7:14                     ` Mateusz Guzik
2024-08-14  3:02                       ` Yin Fengwei
2024-08-14  4:10                         ` Mateusz Guzik
2024-08-14  9:45                           ` David Hildenbrand
2024-08-14 11:06                             ` Mateusz Guzik
2024-08-14 12:02                               ` David Hildenbrand

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=439265d8-e71e-41db-8a46-55366fdd334e@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenhuacai@kernel.org \
    --cc=david@redhat.com \
    --cc=feng.tang@intel.com \
    --cc=jgg@nvidia.com \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=nathan@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).