All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lu, Aaron" <aaron.lu@intel.com>
To: "mhocko@kernel.org" <mhocko@kernel.org>,
	"Ye, Xiaolong" <xiaolong.ye@intel.com>
Cc: "tj@kernel.org" <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lkp@01.org" <lkp@01.org>,
	"hannes@cmpxchg.org" <hannes@cmpxchg.org>
Subject: Re: [LKP] [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement
Date: Tue, 29 May 2018 03:15:51 +0000	[thread overview]
Message-ID: <dbd727326f53648ed114e03a85085b6b4655fda2.camel@intel.com> (raw)
In-Reply-To: <20180528120318.GB27180@dhcp22.suse.cz>

On Mon, 2018-05-28 at 14:03 +0200, Michal Hocko wrote:
> On Mon 28-05-18 19:40:19, kernel test robot wrote:
> > 
> > Greeting,
> > 
> > FYI, we noticed a +23.0% improvement of vm-scalability.throughput due to commit:
> > 
> > 
> > commit: 309fe96bfc0ae387f53612927a8f0dc3eb056efd ("mm, memcontrol: implement memory.swap.events")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> 
> This doesn't make any sense to me. The patch merely adds an accounting.
> It doesn't optimize anything. So I strongly suspect the result is just
> misleading or the test (environment) misconfigured. Not the first time
> I am seeing something like that I am afraid.
> 

Most likely the same situation as:
"
FYI, we noticed a -27.2% regression of will-it-scale.per_process_ops
due to commit:


commit: e27be240df53f1a20c659168e722b5d9f16cc7f4 ("mm: memcg: make sure
memory.events is uptodate when waking pollers")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
"

Where the performance change is due to layout change of
'struct mem_cgroup':
http://lkml.kernel.org/r/20180528085201.GA2918@intel.com

WARNING: multiple messages have this Message-ID (diff)
From: Lu, Aaron <aaron.lu@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement
Date: Tue, 29 May 2018 03:15:51 +0000	[thread overview]
Message-ID: <dbd727326f53648ed114e03a85085b6b4655fda2.camel@intel.com> (raw)
In-Reply-To: <20180528120318.GB27180@dhcp22.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

On Mon, 2018-05-28 at 14:03 +0200, Michal Hocko wrote:
> On Mon 28-05-18 19:40:19, kernel test robot wrote:
> > 
> > Greeting,
> > 
> > FYI, we noticed a +23.0% improvement of vm-scalability.throughput due to commit:
> > 
> > 
> > commit: 309fe96bfc0ae387f53612927a8f0dc3eb056efd ("mm, memcontrol: implement memory.swap.events")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> 
> This doesn't make any sense to me. The patch merely adds an accounting.
> It doesn't optimize anything. So I strongly suspect the result is just
> misleading or the test (environment) misconfigured. Not the first time
> I am seeing something like that I am afraid.
> 

Most likely the same situation as:
"
FYI, we noticed a -27.2% regression of will-it-scale.per_process_ops
due to commit:


commit: e27be240df53f1a20c659168e722b5d9f16cc7f4 ("mm: memcg: make sure
memory.events is uptodate when waking pollers")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
"

Where the performance change is due to layout change of
'struct mem_cgroup':
http://lkml.kernel.org/r/20180528085201.GA2918(a)intel.com

  reply	other threads:[~2018-05-29  4:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 11:40 [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement kernel test robot
2018-05-28 11:40 ` kernel test robot
2018-05-28 12:03 ` Michal Hocko
2018-05-28 12:03   ` Michal Hocko
2018-05-29  3:15   ` Lu, Aaron [this message]
2018-05-29  3:15     ` Lu, Aaron
2018-05-29  7:58     ` [LKP] " Michal Hocko
2018-05-29  7:58       ` Michal Hocko
2018-05-29  8:11       ` [LKP] " Aaron Lu
2018-05-29  8:11         ` Aaron Lu
2018-05-29  8:27         ` [LKP] " Michal Hocko
2018-05-29  8:27           ` Michal Hocko
2018-05-29  9:00           ` [LKP] " Aaron Lu
2018-05-29  9:00             ` Aaron Lu
2018-06-01  7:26 ` [LKP] " Aaron Lu
2018-06-01  7:26   ` Aaron Lu
2018-06-06  8:50   ` [LKP] " Aaron Lu
2018-06-06  8:50     ` Aaron Lu

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=dbd727326f53648ed114e03a85085b6b4655fda2.camel@intel.com \
    --to=aaron.lu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mhocko@kernel.org \
    --cc=tj@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.