[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4fa85b15-1c55-9050-9cd0-fe66c3b957eb@canonical.com>
Date: Fri, 27 Jan 2023 18:34:47 -0800
From: John Johansen <john.johansen@...onical.com>
To: "Yin, Fengwei" <fengwei.yin@...el.com>,
kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
linux-kernel@...r.kernel.org, apparmor@...ts.ubuntu.com,
ying.huang@...el.com, feng.tang@...el.com,
zhengjun.xing@...ux.intel.com
Subject: Re: [linus:master] [apparmor] 1ad22fcc4d: stress-ng.kill.ops_per_sec
-42.5% regression
On 1/27/23 17:37, Yin, Fengwei wrote:
> Hi John,
>
> On 12/31/2022 3:18 PM, kernel test robot wrote:
>>
>> Greeting,
>>
>> FYI, we noticed a -42.5% regression of stress-ng.kill.ops_per_sec due to commit:
>>
>>
>> commit: 1ad22fcc4d0d2fb2e0f35aed555a86d016d5e590 ("apparmor: rework profile->rules to be a list")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> in testcase: stress-ng
>> on test machine: 96 threads 2 sockets Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz (Cascade Lake) with 512G memory
>> with following parameters:
>>
>> nr_threads: 10%
>> disk: 1HDD
>> testtime: 60s
>> fs: ext4
>> class: os
>> test: kill
>> cpufreq_governor: performance
> Do you think any other information need be collected for this regression
> report? Thanks.
>
no, I know what is causing it, I just haven't had time to fix it yet.
Powered by blists - more mailing lists