From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: "Jan Kara" <jack@suse.cz>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Balbir Singh" <bsingharora@gmail.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Hugh Dickins" <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Michal Hocko" <mhocko@kernel.org>,
lkp@01.org, "Minchan Kim" <minchan@kernel.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mel Gorman" <mgorman@suse.de>, "Shaohua Li" <shli@fb.com>,
"Greg Thelen" <gthelen@google.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Tim Chen" <tim.c.chen@linux.intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: [LKP] [lkp-robot] [mm, mlock, vmscan] 9c4e6b1a70: stress-ng.hdd.ops_per_sec -7.9% regression
Date: Mon, 26 Feb 2018 12:56:45 +0800 [thread overview]
Message-ID: <20180226045645.GE3019@yexl-desktop> (raw)
In-Reply-To: <20180226025728.GA8942@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On 02/26, Ye Xiaolong wrote:
>Hi, Shakeel
>
>On 02/25, Shakeel Butt wrote:
>>On Sun, Feb 25, 2018 at 6:44 AM, kernel test robot
>><xiaolong.ye@intel.com> wrote:
>>>
>>> Greeting,
>>>
>>> FYI, we noticed a -7.9% regression of stress-ng.hdd.ops_per_sec due to commit:
>>>
>>>
>>> commit: 9c4e6b1a7027f102990c0395296015a812525f4d ("mm, mlock, vmscan: no more skipping pagevecs")
>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>>
>>> in testcase: stress-ng
>>> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 128G memory
>>> with following parameters:
>>>
>>
>>Hi Xiaolong,
>>
>>Is there a way I can get the output of "perf record -a -g" running in
>>parallel to the actual test on this machine. As I have mentioned
>>before I am not able to reproduce this issue. However I am trying to
>>repro on a VM with 4 vcpus and 4 GiB memory and I don't see any
>>difference. I am suspecting that it may repro on a larger machine but
>>I don't have access to one.
>>
>
>perf.data attached. It was generated via `perf record -q -ag --realtime=1 -m 256`
Attached perf-profile.gz is the result of `perf report` result.
Thanks,
Xiaolong
>
>Thanks,
>Xiaolong
>
>>thanks,
>>Shakeel
>_______________________________________________
>LKP mailing list
>LKP@lists.01.org
>https://lists.01.org/mailman/listinfo/lkp
[-- Attachment #2: perf.data --]
[-- Type: application/octet-stream, Size: 250924 bytes --]
[-- Attachment #3: perf-profile.gz --]
[-- Type: application/octet-stream, Size: 2801 bytes --]
next prev parent reply other threads:[~2018-02-26 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 14:44 [lkp-robot] [mm, mlock, vmscan] 9c4e6b1a70: stress-ng.hdd.ops_per_sec -7.9% regression kernel test robot
2018-02-25 22:03 ` Shakeel Butt
2018-02-26 2:57 ` Ye Xiaolong
2018-02-26 4:56 ` Ye Xiaolong [this message]
2018-02-26 21:24 ` [LKP] " Shakeel Butt
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=20180226045645.GE3019@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=npiggin@gmail.com \
--cc=shakeelb@google.com \
--cc=shli@fb.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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