linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: "Liu, Yujie" <yujie.liu@intel.com>
Cc: lkp <lkp@intel.com>,  "bharata@amd.com" <bharata@amd.com>,
	 "Yin, Fengwei" <fengwei.yin@intel.com>,
	 "willy@infradead.org" <willy@infradead.org>,
	 "mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
	 "shy828301@gmail.com" <shy828301@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xhao@linux.alibaba.com" <xhao@linux.alibaba.com>,
	 "Tang, Feng" <feng.tang@intel.com>,
	 "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>,
	 "ziy@nvidia.com" <ziy@nvidia.com>,
	 "zhengjun.xing@linux.intel.com" <zhengjun.xing@linux.intel.com>,
	 "osalvador@suse.de" <osalvador@suse.de>,
	"baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
	"minchan@kernel.org" <minchan@kernel.org>,
	 "42.hyeyoo@gmail.com" <42.hyeyoo@gmail.com>,
	 "apopple@nvidia.com" <apopple@nvidia.com>
Subject: Re: [linus:master] [migrate_pages] 7e12beb8ca: vm-scalability.throughput -3.4% regression
Date: Thu, 23 Mar 2023 09:53:23 +0800	[thread overview]
Message-ID: <87zg84s06k.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <ce5e09c3a2eceb40048afbad5e6b6856f62d815a.camel@intel.com> (Yujie Liu's message of "Wed, 22 Mar 2023 13:17:54 +0800")

"Liu, Yujie" <yujie.liu@intel.com> writes:

> On Tue, 2023-03-21 at 13:43 +0800, Huang, Ying wrote:
>> "Liu, Yujie" <yujie.liu@intel.com> writes:
>>
>> > Hi Ying,
>> >
>> > On Mon, 2023-03-20 at 15:58 +0800, Huang, Ying wrote:
>> > > Hi, Yujie,
>> > >
>> > > kernel test robot <yujie.liu@intel.com> writes:
>> > >
>> > > > Hello,
>> > > >
>> > > > FYI, we noticed a -3.4% regression of vm-scalability.throughput due to commit:
>> > > >
>> > > > commit: 7e12beb8ca2ac98b2ec42e0ea4b76cdc93b58654 ("migrate_pages: batch flushing TLB")
>> > > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>> > > >
>> > > > in testcase: vm-scalability
>> > > > on test machine: 96 threads 2 sockets Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz (Cascade Lake) with 128G memory
>> > > > with following parameters:
>> > > >
>> > > >         runtime: 300s
>> > > >         size: 512G
>> > > >         test: anon-cow-rand-mt
>> > > >         cpufreq_governor: performance
>> > > >
>> > > > test-description: The motivation behind this suite is to exercise functions and regions of the mm/ of the Linux kernel which are of interest to us.
>> > > > test-url: https://git.kernel.org/cgit/linux/kernel/git/wfg/vm-scalability.git/
>> > > >
>> > > >
>> > > > If you fix the issue, kindly add following tag
>> > > > > Reported-by: kernel test robot <yujie.liu@intel.com>
>> > > > > Link: https://lore.kernel.org/oe-lkp/202303192325.ecbaf968-yujie.liu@intel.com
>> > > >
>> > >
>> > > Thanks a lot for report!  Can you try whether the debug patch as
>> > > below can restore the regression?
>> >
>> > We've tested the patch and found the throughput score was partially
>> > restored from -3.6% to -1.4%, still with a slight performance drop.
>> > Please check the detailed data as follows:
>>
>> Good!  Thanks for your detailed data!
>>
>> >       0.09 ± 17%      +1.2        1.32 ±  7%      +0.4        0.45 ± 21%  perf-profile.children.cycles-pp.flush_tlb_func
>>
>> It appears that we can reduce the unnecessary TLB flushing effectively
>> with the previous debug patch.  But the batched flush (full flush) is
>> still slower than the non-batched flush (flush one page).
>>
>> Can you try the debug patch as below to check whether it can restore the
>> regression completely?  The new debug patch can be applied on top of the
>> previous debug patch.
>
> The second debug patch got a -0.7% performance change. The data have
> some fluctuations from test to test, and the standard deviation is even
> a bit larger than 0.7%, which make the performance score not very
> convincing. Please check other metrics to see if the regression is
> fully restored. Thanks.

Thanks for testing!

>       0.09 ± 17%      +0.4        0.45 ± 21%      +0.0        0.09 ± 12%  perf-profile.children.cycles-pp.flush_tlb_func

From the profiling data, the TLB flushing overhead has been restored.
So I think the remaining 0.7% regression should be at noise level.  I
will prepare the fixing patch based on the test results.

Best Regards,
Huang, Ying


      reply	other threads:[~2023-03-23  1:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  1:12 kernel test robot
2023-03-20  7:58 ` Huang, Ying
2023-03-21  3:24   ` Liu, Yujie
2023-03-21  5:43     ` Huang, Ying
2023-03-22  5:17       ` Liu, Yujie
2023-03-23  1:53         ` Huang, Ying [this message]

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=87zg84s06k.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bharata@amd.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mike.kravetz@oracle.com \
    --cc=minchan@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=osalvador@suse.de \
    --cc=shy828301@gmail.com \
    --cc=willy@infradead.org \
    --cc=xhao@linux.alibaba.com \
    --cc=yujie.liu@intel.com \
    --cc=zhengjun.xing@linux.intel.com \
    --cc=ziy@nvidia.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