From: Michal Hocko <mhocko@kernel.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Minchan Kim <minchan@kernel.org>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression
Date: Tue, 24 Jan 2017 14:44:25 +0100 [thread overview]
Message-ID: <20170124134424.GL6867@dhcp22.suse.cz> (raw)
In-Reply-To: <20170123012644.GD17561@yexl-desktop>
On Mon 23-01-17 09:26:44, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -11.1% regression of fsmark.files_per_sec due to commit:
>
>
> commit: 5e56dfbd837421b7fa3c6c06018c6701e2704917 ("mm, vmscan: consider eligible zones in get_scan_count")
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
This is more than unexpected. This patch should be basically noop for
anything but CONFIG_HIGHMEM systems. And your config says this is 64b
kernel. Are those results reproducible? And could you try to compare
perf profiles before and after the patch.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-01-24 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 1:26 [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression kernel test robot
2017-01-24 13:44 ` Michal Hocko [this message]
2017-01-25 4:27 ` Ye Xiaolong
2017-01-26 9:13 ` Michal Hocko
2017-02-04 8:16 ` Ye Xiaolong
2017-02-06 8:12 ` Michal Hocko
2017-02-07 2:22 ` Ye Xiaolong
2017-02-07 14:43 ` Michal Hocko
2017-02-23 1:27 ` Ye Xiaolong
2017-02-23 7:35 ` Michal Hocko
2017-02-23 15:19 ` Mel Gorman
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=20170124134424.GL6867@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@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