From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Oliver Sang <oliver.sang@intel.com>, Yang Shi <shy828301@gmail.com>
Cc: Rik van Riel <riel@surriel.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Christopher Lameter <cl@linux.com>, <ying.huang@intel.com>,
<feng.tang@intel.com>
Subject: Re: [linux-next:master] [mm] 1111d46b5c: stress-ng.pthread.ops_per_sec -84.3% regression
Date: Fri, 5 Jan 2024 22:52:19 +0800 [thread overview]
Message-ID: <6bf7037f-e1ad-453d-adb1-37be748a1364@intel.com> (raw)
In-Reply-To: <ZZfL6APUYZ3VuUTv@xsang-OptiPlex-9020>
On 1/5/2024 5:29 PM, Oliver Sang wrote:
> hi, Yang Shi,
>
> On Thu, Jan 04, 2024 at 04:39:50PM +0800, Oliver Sang wrote:
>> hi, Fengwei, hi, Yang Shi,
>>
>> On Thu, Jan 04, 2024 at 04:18:00PM +0800, Yin Fengwei wrote:
>>>
>>> On 2024/1/4 09:32, Yang Shi wrote:
>>
>> ...
>>
>>>> Can you please help test the below patch?
>>> I can't access the testing box now. Oliver will help to test your patch.
>>>
>>
>> since now the commit-id of
>> 'mm: align larger anonymous mappings on THP boundaries'
>> in linux-next/master is efa7df3e3bb5d
>> I applied the patch like below:
>>
>> * d8d7b1dae6f03 fix for 'mm: align larger anonymous mappings on THP boundaries' from Yang Shi
>> * efa7df3e3bb5d mm: align larger anonymous mappings on THP boundaries
>> * 1803d0c5ee1a3 mailmap: add an old address for Naoya Horiguchi
>>
>> our auto-bisect captured new efa7df3e3b as fbc for quite a number of regression
>> so far, I will test d8d7b1dae6f03 for all these tests. Thanks
>>
>
> we got 12 regressions and 1 improvement results for efa7df3e3b so far.
> (4 regressions are just similar to what we reported for 1111d46b5c).
> by your patch, 6 of those regressions are fixed, others are not impacted.
>
> below is a summary:
>
> No. testsuite test status-on-efa7df3e3b fix-by-d8d7b1dae6 ?
> === ========= ==== ==================== ===================
> (1) stress-ng numa regression NO
> (2) pthread regression yes (on a Ice Lake server)
> (3) pthread regression yes (on a Cascade Lake desktop)
> (4) will-it-scale malloc1 regression NO
> (5) page_fault1 improvement no (so still improvement)
> (6) vm-scalability anon-w-seq-mt regression yes
> (7) stream nr_threads=25% regression yes
> (8) nr_threads=50% regression yes
> (9) phoronix osbench.CreateThreads regression yes (on a Cascade Lake server)
> (10) ramspeed.Add.Integer regression NO (and below 3, on a Coffee Lake desktop)
> (11) ramspeed.Average.FloatingPoint regression NO
> (12) ramspeed.Triad.Integer regression NO
> (13) ramspeed.Average.Integer regression NO
Hints on ramspeed just for your reference:
I did standalone ramspeed (not phoronix) testing on a IceLake 48C/96T +
192GB memory and didn't see the regressions on that testing box (The
testing box was retired at the end of last year and can't be accessed
anymore).
Regards
Yin, Fengwei
next prev parent reply other threads:[~2024-01-05 14:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:41 [linux-next:master] [mm] 1111d46b5c: stress-ng.pthread.ops_per_sec -84.3% regression kernel test robot
2023-12-20 5:27 ` Yang Shi
2023-12-20 8:29 ` Yin Fengwei
2023-12-20 15:42 ` Christoph Lameter (Ampere)
2023-12-20 20:14 ` Yang Shi
2023-12-20 20:09 ` Yang Shi
2023-12-21 0:26 ` Yang Shi
2023-12-21 0:58 ` Yin Fengwei
2023-12-21 1:02 ` Yin Fengwei
2023-12-21 4:49 ` Matthew Wilcox
2023-12-21 4:58 ` Yin Fengwei
2023-12-21 18:07 ` Yang Shi
2023-12-21 18:14 ` Matthew Wilcox
2023-12-22 1:06 ` Yin, Fengwei
2023-12-22 2:23 ` Huang, Ying
2023-12-21 13:39 ` Yin, Fengwei
2023-12-21 18:11 ` Yang Shi
2023-12-22 1:13 ` Yin, Fengwei
2024-01-04 1:32 ` Yang Shi
2024-01-04 8:18 ` Yin Fengwei
2024-01-04 8:39 ` Oliver Sang
2024-01-05 9:29 ` Oliver Sang
2024-01-05 14:52 ` Yin, Fengwei [this message]
2024-01-05 18:49 ` Yang Shi
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=6bf7037f-e1ad-453d-adb1-37be748a1364@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=feng.tang@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=riel@surriel.com \
--cc=shy828301@gmail.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