From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: linux-mm@kvack.org, tglx@linutronix.de,
Vlastimil Babka <vbabka@suse.cz>,
frederic@kernel.org, lkp@01.org
Subject: Re: [LKP] [mm/swap] d884021f52: will-it-scale.per_process_ops -2.4% regression
Date: Sun, 30 Sep 2018 10:17:04 +0200 [thread overview]
Message-ID: <20180930081704.ncajd6rv23qnv237@linutronix.de> (raw)
In-Reply-To: <20180930031640.GG15893@shao2-debian>
On 2018-09-30 11:16:41 [+0800], kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -2.4% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit: d884021f52609407c7943705b3e54b1642fa10cb ("[PATCH 1/2] mm/swap: Add pagevec locking")
-2.4% regression reads to me like an improvement of 2.4%. Which is odd
because I wouldn't expect a change in behaviour from 1/2. 2/2 yes, under
certain workloads but not from 1/2.
Sebastian
next prev parent reply other threads:[~2018-09-30 8:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:59 [PATCH 0/2] mm/swap: Add locking for pagevec Sebastian Andrzej Siewior
2018-09-14 14:59 ` [PATCH 1/2] mm/swap: Add pagevec locking Sebastian Andrzej Siewior
2018-09-30 3:16 ` [LKP] [mm/swap] d884021f52: will-it-scale.per_process_ops -2.4% regression kernel test robot
2018-09-30 8:17 ` Sebastian Andrzej Siewior [this message]
2018-09-14 14:59 ` [PATCH 2/2] mm/swap: Access struct pagevec remotely Sebastian Andrzej Siewior
2018-11-09 23:06 ` Andrew Morton
2018-10-12 7:21 ` [PATCH 0/2] mm/swap: Add locking for pagevec Vlastimil Babka
2018-10-15 9:50 ` Mel Gorman
2018-10-16 16:26 ` Frederic Weisbecker
2018-10-16 17:13 ` Thomas Gleixner
2018-10-16 19:54 ` Frederic Weisbecker
2018-10-16 20:44 ` Thomas Gleixner
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=20180930081704.ncajd6rv23qnv237@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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).