From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
kernel test robot <xiaolong.ye@intel.com>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Adam Borowski <kilobyte@angband.pl>,
Brian Gerst <brgerst@gmail.com>,
Johannes Hirte <johannes.hirte@datenkhaos.de>, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression
Date: Tue, 17 Oct 2017 06:57:43 +0200 [thread overview]
Message-ID: <20171017045743.GA237@x4> (raw)
In-Reply-To: <CALCETrW3G_RfMNKvw0katFuV6dB7k4AfUdVRZ603HNjY=bD4GQ@mail.gmail.com>
On 2017.10.16 at 18:06 -0700, Andy Lutomirski wrote:
> On Mon, Oct 16, 2017 at 3:15 AM, Borislav Petkov <bp@alien8.de> wrote:
> > On Mon, Oct 16, 2017 at 10:39:17AM +0800, kernel test robot wrote:
> >>
> >> Greeting,
> >>
> >> FYI, we noticed a -61.0% regression of will-it-scale.per_process_ops due to commit:
I think you are reading this wrong:
-61.0% regression means 61.0% improvement.
--
Markus
next prev parent reply other threads:[~2017-10-17 4:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 16:50 [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode Andy Lutomirski
2017-10-09 17:02 ` Borislav Petkov
2017-10-09 17:36 ` Borislav Petkov
2017-10-09 17:50 ` Andy Lutomirski
2017-10-09 18:08 ` Borislav Petkov
2017-10-09 18:31 ` Andy Lutomirski
2017-10-13 9:07 ` demfloro
2017-10-14 10:49 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-10-14 12:34 ` [PATCH] x86/mm: Rip out the TLB benchmarking knob Borislav Petkov
2017-10-14 17:01 ` Andy Lutomirski
2017-10-14 16:34 ` [tip:x86/urgent] x86/mm: Flush more aggressively in lazy TLB mode Andy Lutomirski
2017-10-14 17:00 ` Andy Lutomirski
2017-10-16 2:39 ` [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression kernel test robot
2017-10-16 2:39 ` kernel test robot
2017-10-16 10:15 ` Borislav Petkov
2017-10-16 10:15 ` Borislav Petkov
2017-10-17 1:06 ` Andy Lutomirski
2017-10-17 1:06 ` Andy Lutomirski
2017-10-17 4:57 ` Markus Trippelsdorf [this message]
2017-10-17 8:00 ` Borislav Petkov
2017-10-17 8:00 ` Borislav Petkov
2017-10-17 22:06 ` Andy Lutomirski
2017-10-17 22:06 ` Andy Lutomirski
2017-10-18 14:26 ` Borislav Petkov
2017-10-18 14:26 ` Borislav Petkov
2017-10-18 1:59 ` Ye Xiaolong
2017-10-18 1:59 ` Ye Xiaolong
2017-10-18 8:11 ` Borislav Petkov
2017-10-18 8:11 ` Borislav Petkov
2017-10-19 5:57 ` Ye Xiaolong
2017-10-17 6:04 ` Ye Xiaolong
2017-10-17 6:04 ` Ye Xiaolong
2017-10-10 8:22 ` [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode Markus Trippelsdorf
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=20171017045743.GA237@x4 \
--to=markus@trippelsdorf.de \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=johannes.hirte@datenkhaos.de \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=x86@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.