From: Michal Hocko <mhocko@kernel.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement
Date: Mon, 28 May 2018 14:03:18 +0200 [thread overview]
Message-ID: <20180528120318.GB27180@dhcp22.suse.cz> (raw)
In-Reply-To: <20180528114019.GF9904@yexl-desktop>
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.
--
Michal Hocko
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement
Date: Mon, 28 May 2018 14:03:18 +0200 [thread overview]
Message-ID: <20180528120318.GB27180@dhcp22.suse.cz> (raw)
In-Reply-To: <20180528114019.GF9904@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
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.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-05-28 15:54 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 [this message]
2018-05-28 12:03 ` Michal Hocko
2018-05-29 3:15 ` [LKP] " Lu, Aaron
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=20180528120318.GB27180@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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.