From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751145AbdAXNop (ORCPT ); Tue, 24 Jan 2017 08:44:45 -0500 Received: from mx2.suse.de ([195.135.220.15]:45311 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750930AbdAXNom (ORCPT ); Tue, 24 Jan 2017 08:44:42 -0500 Date: Tue, 24 Jan 2017 14:44:25 +0100 From: Michal Hocko To: kernel test robot Cc: Stephen Rothwell , Minchan Kim , Hillf Danton , Mel Gorman , Johannes Weiner , Andrew Morton , LKML , lkp@01.org Subject: Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression Message-ID: <20170124134424.GL6867@dhcp22.suse.cz> References: <20170123012644.GD17561@yexl-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170123012644.GD17561@yexl-desktop> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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