From: Kees Cook <keescook@chromium.org>
To: lkp@lists.01.org
Subject: Re: [PCI] dc83615370: will-it-scale.per_process_ops -1.2% regression
Date: Tue, 12 Jan 2021 09:30:46 -0800 [thread overview]
Message-ID: <202101120927.B3345B30@keescook> (raw)
In-Reply-To: <20210112141045.GD30747@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
On Tue, Jan 12, 2021 at 10:10:45PM +0800, kernel test robot wrote:
> FYI, we noticed a -1.2% regression of will-it-scale.per_process_ops due to commit:
>
> commit: dc83615370e7ebcb181a21a8ad13a77c278ab81c ("PCI: Fix PREL32 relocations for LTO")
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git for-next/kspp
O_o Well that's surprising. This only creates stubs.
> will-it-scale.workload
>
> 2.14e+07 +----------------------------------------------------------------+
> |.+. .+ : + +.+. +.+. .+ +.+. .+ : |
> 2.13e+07 |-+ + : +.+ + + + + : |
> | : : + .+.+..+. .+ +. |
> 2.12e+07 |-+ : : + + +.+.|
> | +.+ |
> 2.11e+07 |-+ |
> | |
> 2.1e+07 |-+ O O O O O O O |
> | O O O O O O O O O |
> 2.09e+07 |-+ O |
> | O O |
> 2.08e+07 |-O O O O O |
> | |
> 2.07e+07 +----------------------------------------------------------------+
>
>
> [*] bisect-good sample
> [O] bisect-bad sample
But it's pretty clear _something_ has happened. We'll investigate...
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com
Subject: Re: [PCI] dc83615370: will-it-scale.per_process_ops -1.2% regression
Date: Tue, 12 Jan 2021 09:30:46 -0800 [thread overview]
Message-ID: <202101120927.B3345B30@keescook> (raw)
In-Reply-To: <20210112141045.GD30747@xsang-OptiPlex-9020>
On Tue, Jan 12, 2021 at 10:10:45PM +0800, kernel test robot wrote:
> FYI, we noticed a -1.2% regression of will-it-scale.per_process_ops due to commit:
>
> commit: dc83615370e7ebcb181a21a8ad13a77c278ab81c ("PCI: Fix PREL32 relocations for LTO")
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git for-next/kspp
O_o Well that's surprising. This only creates stubs.
> will-it-scale.workload
>
> 2.14e+07 +----------------------------------------------------------------+
> |.+. .+ : + +.+. +.+. .+ +.+. .+ : |
> 2.13e+07 |-+ + : +.+ + + + + : |
> | : : + .+.+..+. .+ +. |
> 2.12e+07 |-+ : : + + +.+.|
> | +.+ |
> 2.11e+07 |-+ |
> | |
> 2.1e+07 |-+ O O O O O O O |
> | O O O O O O O O O |
> 2.09e+07 |-+ O |
> | O O |
> 2.08e+07 |-O O O O O |
> | |
> 2.07e+07 +----------------------------------------------------------------+
>
>
> [*] bisect-good sample
> [O] bisect-bad sample
But it's pretty clear _something_ has happened. We'll investigate...
--
Kees Cook
next prev parent reply other threads:[~2021-01-12 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 14:10 [PCI] dc83615370: will-it-scale.per_process_ops -1.2% regression kernel test robot
2021-01-12 14:10 ` kernel test robot
2021-01-12 17:30 ` Kees Cook [this message]
2021-01-12 17:30 ` Kees Cook
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=202101120927.B3345B30@keescook \
--to=keescook@chromium.org \
--cc=lkp@lists.01.org \
/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.