From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: John Johansen <john.johansen@canonical.com>,
kernel test robot <oliver.sang@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <apparmor@lists.ubuntu.com>,
<ying.huang@intel.com>, <feng.tang@intel.com>,
<zhengjun.xing@linux.intel.com>
Subject: Re: [linus:master] [apparmor] 1ad22fcc4d: stress-ng.kill.ops_per_sec -42.5% regression
Date: Sat, 28 Jan 2023 11:05:52 +0800 [thread overview]
Message-ID: <9e4d012f-6ff6-aef4-a70d-cc9f1478921a@intel.com> (raw)
In-Reply-To: <4fa85b15-1c55-9050-9cd0-fe66c3b957eb@canonical.com>
On 1/28/2023 10:34 AM, John Johansen wrote:
> 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.
Great. Let us know if you want us to try something out. Thanks.
Regards
Yin, Fengwei
>
prev parent reply other threads:[~2023-01-28 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 7:18 kernel test robot
2023-01-28 1:37 ` Yin, Fengwei
2023-01-28 2:34 ` John Johansen
2023-01-28 3:05 ` Yin, Fengwei [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=9e4d012f-6ff6-aef4-a70d-cc9f1478921a@intel.com \
--to=fengwei.yin@intel.com \
--cc=apparmor@lists.ubuntu.com \
--cc=feng.tang@intel.com \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@linux.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
all inboxes | Powered by JetHome®