lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170126091317.GB6590@dhcp22.suse.cz>
Date:   Thu, 26 Jan 2017 10:13:18 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Ye Xiaolong <xiaolong.ye@...el.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Minchan Kim <minchan@...nel.org>,
        Hillf Danton <hillf.zj@...baba-inc.com>,
        Mel Gorman <mgorman@...e.de>,
        Johannes Weiner <hannes@...xchg.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [lkp-robot] [mm, vmscan]  5e56dfbd83:  fsmark.files_per_sec
 -11.1% regression

On Wed 25-01-17 12:27:06, Ye Xiaolong wrote:
> On 01/24, Michal Hocko wrote:
> >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
> 
> Yes, the results are well reproducible, both the commit in question and its
> parent have ran for 4 times.
> 
> >perf profiles before and after the patch.
> 
> Here is the perf profiles, 

I do not see any reclaim path in the profile... Could you take a
snapshot of /proc/vmstat and /proc/zoneinfo before and after the test
please?

-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ