linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nikhil Dhama <nikhil.dhama@amd.com>
To: <oliver.sang@intel.com>
Cc: <akpm@linux-foundation.org>, <bharata@amd.com>,
	<huang.ying.caritas@gmail.com>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>, <mgorman@techsingularity.net>,
	<nikhil.dhama@amd.com>, <oe-lkp@lists.linux.dev>,
	<raghavendra.kt@amd.com>, <ying.huang@linux.alibaba.com>
Subject: Re: [linus:master] [mm]  c544a952ba:  netperf.Throughput_Mbps 18.9%
Date: Wed, 9 Jul 2025 14:50:46 +0530	[thread overview]
Message-ID: <20250709092046.10428-1-nikhil.dhama@amd.com> (raw)
In-Reply-To: <202507030638.d8cff1fb-lkp@intel.com>

Hi,

On 7/3/2025 11:19 AM, kernel test robot wrote:
>
> Hello,
>
>
> we reported
> "[linus:master] [mm]  c544a952ba:  vm-scalability.throughput 33.3% improvement"
> in
> https://lore.kernel.org/all/202506121415.eeceda1d-lkp@intel.com/
>
> now we captured a netperf regression on a Core machine.
>
> we don't have enough knowledge if this is a tradeoff, just make out this report
> FYI.
>
>
> kernel test robot noticed a 18.9% regression of netperf.Throughput_Mbps on:
>

[...]

> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20250703/202507030638.d8cff1fb-lkp@intel.com

I tried reproducing this issue using the shared kernel config,
On a 192 cores AMD EPYC server with 768G memory, 
I am getting following score (normalised wrt v6.15 vanilla):

                      netperf UDP_STREAM
                      ------------------       
v6.15 vanilla                 	     100
v6.15 with (c544a952ba)          100.085



> commit: c544a952ba61b1a025455098033c17e0573ab085 ("mm: pcp: increase pcp->free_count threshold to trigger free_high")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [still regression on linus/master      66701750d5565c574af42bef0b789ce0203e3071]
> [still regression on linux-next/master 3f804361f3b9af33e00b90ec9cb5afcc96831e60]
>
> testcase: netperf
> config: x86_64-rhel-9.4
> compiler: gcc-12
> test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
> parameters:
>
>         ip: ipv4
>         runtime: 300s
>         nr_threads: 1
>         cluster: cs-localhost
>         test: UDP_STREAM
>         cpufreq_governor: performance

To match thread count and memory, On the same machine I disabled all cpus
keeping only 4 of them enabled, and limited memory to 32G.

with this configuration, I am getting the following score:

                      netperf UDP_STREAM
                      ------------------
v6.15 vanilla                        100
v6.15 with (c544a952ba)              154

I am not able to repoduce the issue, am I missing something which is required to reproduce?

Thanks,
Nikhil


      reply	other threads:[~2025-07-09  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  5:49 [linus:master] [mm] c544a952ba: netperf.Throughput_Mbps 18.9% regression kernel test robot
2025-07-09  9:20 ` Nikhil Dhama [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=20250709092046.10428-1-nikhil.dhama@amd.com \
    --to=nikhil.dhama@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharata@amd.com \
    --cc=huang.ying.caritas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=raghavendra.kt@amd.com \
    --cc=ying.huang@linux.alibaba.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