From: Boris Petkov <bp@alien8.de>
To: Manikandan Jagatheesan <mjagatheesan@vmware.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
Kodeswaran Kumarasamy <kkumarasamy@vmware.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Abdul Anshad Azeez <aazees@vmware.com>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
Peter Jonasson <pjonasson@vmware.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
Yiu Cho Lau <lauyiuch@vmware.com>, Rajender M <manir@vmware.com>,
Rahul Gopakumar <gopakumarr@vmware.com>
Subject: Re: Performance Regression in Linux Kernel 5.19
Date: Tue, 13 Sep 2022 10:27:53 +0000 [thread overview]
Message-ID: <66C9A8CD-C4FF-4E41-8F5A-FF58FE4F24E2@alien8.de> (raw)
In-Reply-To: <PH0PR05MB84483065597B17B361CBA9ABAF479@PH0PR05MB8448.namprd05.prod.outlook.com>
On September 13, 2022 8:40:49 AM UTC, Manikandan Jagatheesan <mjagatheesan@vmware.com> wrote:
>Are there are any ongoing activities to optimize the performance?
What do you think is there to optimize here? Might wanna read my reply again...
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2022-09-13 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 11:46 Performance Regression in Linux Kernel 5.19 Manikandan Jagatheesan
2022-09-09 13:18 ` Peter Zijlstra
2022-09-09 21:22 ` David Laight
2022-09-10 7:52 ` Borislav Petkov
2022-09-12 10:58 ` Borislav Petkov
2022-09-13 8:40 ` Manikandan Jagatheesan
2022-09-13 10:27 ` Boris Petkov [this message]
2022-09-13 11:20 ` Peter Zijlstra
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=66C9A8CD-C4FF-4E41-8F5A-FF58FE4F24E2@alien8.de \
--to=bp@alien8.de \
--cc=aazees@vmware.com \
--cc=dave.hansen@linux.intel.com \
--cc=gopakumarr@vmware.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kkumarasamy@vmware.com \
--cc=lauyiuch@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manir@vmware.com \
--cc=mingo@redhat.com \
--cc=mjagatheesan@vmware.com \
--cc=peterz@infradead.org \
--cc=pjonasson@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).