From: Thomas Gleixner <tglx@linutronix.de>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@intel.com
Subject: Re: [signal] 4bad58ebc8: will-it-scale.per_thread_ops -3.3% regression
Date: Thu, 22 Apr 2021 17:37:18 +0200 [thread overview]
Message-ID: <87eef2xrdd.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210422060213.GC31382@xsang-OptiPlex-9020>
Oliver,
On Thu, Apr 22 2021 at 14:02, Oliver Sang wrote:
> On Tue, Apr 20, 2021 at 08:35:06PM +0200, Thomas Gleixner wrote:
>> Confused.
>
> FYI.
> we re-test this, and confirmed the regression persistent. still:
>
> 69995ebbb9d37173 4bad58ebc8bc4f20d89cff95417
> ---------------- ---------------------------
> %stddev %change %stddev
> \ | \
> 1.271e+09 -3.3% 1.229e+09 will-it-scale.192.threads
> 6620228 -3.3% 6401749 will-it-scale.per_thread_ops
> 1.271e+09 -3.3% 1.229e+09 will-it-scale.workload
I'll have a look.
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: lkp@lists.01.org
Subject: Re: [signal] 4bad58ebc8: will-it-scale.per_thread_ops -3.3% regression
Date: Thu, 22 Apr 2021 17:37:18 +0200 [thread overview]
Message-ID: <87eef2xrdd.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210422060213.GC31382@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Oliver,
On Thu, Apr 22 2021 at 14:02, Oliver Sang wrote:
> On Tue, Apr 20, 2021 at 08:35:06PM +0200, Thomas Gleixner wrote:
>> Confused.
>
> FYI.
> we re-test this, and confirmed the regression persistent. still:
>
> 69995ebbb9d37173 4bad58ebc8bc4f20d89cff95417
> ---------------- ---------------------------
> %stddev %change %stddev
> \ | \
> 1.271e+09 -3.3% 1.229e+09 will-it-scale.192.threads
> 6620228 -3.3% 6401749 will-it-scale.per_thread_ops
> 1.271e+09 -3.3% 1.229e+09 will-it-scale.workload
I'll have a look.
next prev parent reply other threads:[~2021-04-22 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 3:08 [signal] 4bad58ebc8: will-it-scale.per_thread_ops -3.3% regression kernel test robot
2021-04-20 3:08 ` kernel test robot
2021-04-20 18:35 ` Thomas Gleixner
2021-04-20 18:35 ` Thomas Gleixner
2021-04-22 6:02 ` Oliver Sang
2021-04-22 6:02 ` Oliver Sang
2021-04-22 15:37 ` Thomas Gleixner [this message]
2021-04-22 15:37 ` Thomas Gleixner
2021-04-30 8:13 ` Feng Tang
2021-04-30 8:13 ` Feng Tang
2021-04-30 8:57 ` Thomas Gleixner
2021-04-30 8:57 ` Thomas Gleixner
2021-05-01 9:46 ` Feng Tang
2021-05-01 9:46 ` Feng Tang
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=87eef2xrdd.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oleg@redhat.com \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=zhengjun.xing@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.