From: Rahul Gopakumar <gopakumarr@vmware.com>
To: "bhe@redhat.com" <bhe@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"natechancellor@gmail.com" <natechancellor@gmail.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"clang-built-linux@googlegroups.com"
<clang-built-linux@googlegroups.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Rajender M <manir@vmware.com>, Yiu Cho Lau <lauyiuch@vmware.com>,
Peter Jonasson <pjonasson@vmware.com>,
Venkatesh Rajaram <rajaramv@vmware.com>
Subject: Re: Performance regressions in "boot_time" tests in Linux 5.8 Kernel
Date: Fri, 20 Nov 2020 03:11:11 +0000 [thread overview]
Message-ID: <DM6PR05MB52920B2D4267AD7D073D3C36A4FF0@DM6PR05MB5292.namprd05.prod.outlook.com> (raw)
In-Reply-To: <20201112145149.GN8486@MiWiFi-R3L-srv>
Hi Baoquan,
To which commit should we apply the draft patch. We tried applying
the patch to the commit 3e4fb4346c781068610d03c12b16c0cfb0fd24a3
(the one we used for applying the previous patch) but it fails.
From: bhe@redhat.com <bhe@redhat.com>
Sent: 12 November 2020 8:21 PM
To: Rahul Gopakumar <gopakumarr@vmware.com>
Cc: linux-mm@kvack.org <linux-mm@kvack.org>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; akpm@linux-foundation.org <akpm@linux-foundation.org>; natechancellor@gmail.com <natechancellor@gmail.com>; ndesaulniers@google.com <ndesaulniers@google.com>; clang-built-linux@googlegroups.com <clang-built-linux@googlegroups.com>; rostedt@goodmis.org <rostedt@goodmis.org>; Rajender M <manir@vmware.com>; Yiu Cho Lau <lauyiuch@vmware.com>; Peter Jonasson <pjonasson@vmware.com>; Venkatesh Rajaram <rajaramv@vmware.com>
Subject: Re: Performance regressions in "boot_time" tests in Linux 5.8 Kernel
On 11/03/20 at 12:34pm, Rahul Gopakumar wrote:
> >> So, you mean with the draft patch applied, the initial performance
> regression goes away, just many page corruption errors with call trace
> are seen, right?
>
> Yes, that's right.
>
> >> And the performance regression is about 2sec delay in
> your system?
>
> The delay due to this new page corruption issue is about
> 3 secs.
>
> Here is the summary
>
> * Initial problem - 2 secs
> * Draft patch - Fixes initial problem (recovers 2 secs) but
> brings in new page corruption issue (3 secs)
>
> >> Could you tell how you setup vmware VM so that I can ask our QA for
> help to create a vmware VM for me to test?
>
> * Use vSphere ESXi 6.7 or 7.0 GA.
> * Create VM using vSphere Web Client and specify 1TB VM Memory.
> * Install RHEL 8.1, that's the guest used in this test.
Can you try the attached draft patch?
>
> With draft patch, you should be able to reproduce the issue.
> Let me know if you need more details.
next prev parent reply other threads:[~2020-11-20 3:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 13:15 Rahul Gopakumar
2020-10-10 6:11 ` bhe
2020-10-12 17:21 ` Rahul Gopakumar
2020-10-13 5:08 ` bhe
2020-10-13 13:17 ` bhe
2020-10-20 13:45 ` Rahul Gopakumar
2020-10-20 15:18 ` bhe
2020-10-20 15:26 ` Rahul Gopakumar
2020-10-22 4:04 ` bhe
2020-10-22 17:21 ` Rahul Gopakumar
2020-11-02 14:15 ` Rahul Gopakumar
2020-11-02 14:30 ` bhe
2020-11-03 12:34 ` Rahul Gopakumar
2020-11-03 14:03 ` bhe
2020-11-12 14:51 ` bhe
2020-11-20 3:11 ` Rahul Gopakumar [this message]
2020-11-22 1:08 ` bhe
2020-11-24 15:03 ` Rahul Gopakumar
2020-11-30 16:55 ` Mike Rapoport
2020-12-11 16:16 ` Rahul Gopakumar
2020-12-13 15:15 ` bhe
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=DM6PR05MB52920B2D4267AD7D073D3C36A4FF0@DM6PR05MB5292.namprd05.prod.outlook.com \
--to=gopakumarr@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=lauyiuch@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manir@vmware.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pjonasson@vmware.com \
--cc=rajaramv@vmware.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox