linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Hugh Dickins <hughd@google.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: [lkp] [shmem]  071904e8df: meminfo.AnonHugePages +553.5% increase
Date: Thu, 4 Aug 2016 12:54:11 +0300	[thread overview]
Message-ID: <20160804095411.GB12395@node.shutemov.name> (raw)
In-Reply-To: <20160804085409.GI19697@yexl-desktop>

On Thu, Aug 04, 2016 at 04:54:09PM +0800, kernel test robot wrote:
> 
> FYI, we noticed meminfo.AnonHugePages +553.5% increase due to commit:
> 
> commit 071904e8dfed9525f9da86523caf78b6da5f9e7e ("shmem: get_unmapped_area align huge page")
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> 
> in testcase: vm-scalability
> on test machine: 128 threads 4 Sockets Haswell-EP with 512G memory
> with following parameters:
> 
> 	path_params: 300s-16G-shm-pread-rand-mt-performance
> 	run: 
> 
> 
> 
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
> 
> Details are as below:
> -------------------------------------------------------------------------------------------------->
> 
> 
> 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
> 
> =========================================================================================
> compiler/cpufreq_governor/kconfig/rootfs/runtime/size/tbox_group/test/testcase:
>   gcc-6/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/300s/16G/lkp-hsw-4ep1/shm-pread-rand-mt/vm-scalability
> 
> commit: 
>   6a028aa3ca ("shmem: prepare huge= mount option and sysfs knob")
>   071904e8df ("shmem: get_unmapped_area align huge page")
> 
> 6a028aa3ca32379e 071904e8dfed9525f9da86523c 
> ---------------- -------------------------- 
>          %stddev     %change         %stddev
>              \          |                \  
>      20428 ±  9%    +553.5%     133500 ±  7%  meminfo.AnonHugePages
>      42717 ±  4%    +261.3%     154340 ±  6%  meminfo.AnonPages

Hm. That's strange. I didn't expect this commit change anything for anon
memory.

Do you see the same effect from the commit in Linus' tree?

-- 
 Kirill A. Shutemov

  parent reply	other threads:[~2016-08-04 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04  8:54 [lkp] [shmem] 071904e8df: meminfo.AnonHugePages +553.5% increase kernel test robot
2016-08-04  9:10 ` Andrew Morton
2016-08-04  9:54 ` Kirill A. Shutemov [this message]
2016-08-05  3:17   ` Ye Xiaolong

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=20160804095411.GB12395@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.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;
as well as URLs for NNTP newsgroup(s).