From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753095AbcD0JR2 (ORCPT ); Wed, 27 Apr 2016 05:17:28 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36198 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752614AbcD0JRW (ORCPT ); Wed, 27 Apr 2016 05:17:22 -0400 Date: Wed, 27 Apr 2016 11:17:19 +0200 From: Michal Hocko To: "Huang, Ying" Cc: kernel test robot , Stephen Rothwell , Tetsuo Handa , Hillf Danton , LKML , Johannes Weiner , Mel Gorman , David Rientjes , Andrew Morton , lkp@01.org, KAMEZAWA Hiroyuki Subject: Re: [LKP] [lkp] [mm, oom] faad2185f4: vm-scalability.throughput -11.8% regression Message-ID: <20160427091718.GG2179@dhcp22.suse.cz> References: <20160427031556.GD29014@yexl-desktop> <20160427073617.GA2179@dhcp22.suse.cz> <87fuu7iht0.fsf@yhuang-dev.intel.com> <20160427083733.GE2179@dhcp22.suse.cz> <87bn4vigpc.fsf@yhuang-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87bn4vigpc.fsf@yhuang-dev.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 27-04-16 16:44:31, Huang, Ying wrote: > Michal Hocko writes: > > > On Wed 27-04-16 16:20:43, Huang, Ying wrote: > >> Michal Hocko writes: > >> > >> > On Wed 27-04-16 11:15:56, kernel test robot wrote: > >> >> FYI, we noticed vm-scalability.throughput -11.8% regression with the following commit: > >> > > >> > Could you be more specific what the test does please? > >> > >> The sub-testcase of vm-scalability is swap-w-rand. An RAM emulated pmem > >> device is used as a swap device, and a test program will allocate/write > >> anonymous memory randomly to exercise page allocation, reclaiming, and > >> swapping in code path. > > > > Can I download the test with the setup to play with this? > > There are reproduce steps in the original report email. > > To reproduce: > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git > cd lkp-tests > bin/lkp install job.yaml # job file is attached in this email > bin/lkp run job.yaml > > > The job.yaml and kconfig file are attached in the original report email. Thanks for the instructions. My bad I have overlooked that in the initial email. I have checked the configuration file and it seems rather hardcoded for a particular HW. It expects a machine with 128G and reserves 96G!4G which might lead to different amount of memory in the end depending on the particular memory layout. Before I go and try to recreate a similar setup, how stable are the results from this test. Random access pattern sounds like rather volatile to be consider for a throughput test. Or is there any other side effect I am missing and something fails which didn't use to previously. -- Michal Hocko SUSE Labs From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8243862028537595176==" MIME-Version: 1.0 From: Michal Hocko To: lkp@lists.01.org Subject: Re: [mm, oom] faad2185f4: vm-scalability.throughput -11.8% regression Date: Wed, 27 Apr 2016 11:17:19 +0200 Message-ID: <20160427091718.GG2179@dhcp22.suse.cz> In-Reply-To: <87bn4vigpc.fsf@yhuang-dev.intel.com> List-Id: --===============8243862028537595176== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed 27-04-16 16:44:31, Huang, Ying wrote: > Michal Hocko writes: > = > > On Wed 27-04-16 16:20:43, Huang, Ying wrote: > >> Michal Hocko writes: > >> = > >> > On Wed 27-04-16 11:15:56, kernel test robot wrote: > >> >> FYI, we noticed vm-scalability.throughput -11.8% regression with th= e following commit: > >> > > >> > Could you be more specific what the test does please? > >> = > >> The sub-testcase of vm-scalability is swap-w-rand. An RAM emulated pm= em > >> device is used as a swap device, and a test program will allocate/write > >> anonymous memory randomly to exercise page allocation, reclaiming, and > >> swapping in code path. > > > > Can I download the test with the setup to play with this? > = > There are reproduce steps in the original report email. > = > To reproduce: > = > git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-t= ests.git > cd lkp-tests > bin/lkp install job.yaml # job file is attached in this email > bin/lkp run job.yaml > = > = > The job.yaml and kconfig file are attached in the original report email. Thanks for the instructions. My bad I have overlooked that in the initial email. I have checked the configuration file and it seems rather hardcoded for a particular HW. It expects a machine with 128G and reserves 96G!4G which might lead to different amount of memory in the end depending on the particular memory layout. Before I go and try to recreate a similar setup, how stable are the results from this test. Random access pattern sounds like rather volatile to be consider for a throughput test. Or is there any other side effect I am missing and something fails which didn't use to previously. -- = Michal Hocko SUSE Labs --===============8243862028537595176==--