mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Manikandan Jagatheesan' <mjagatheesan@vmware.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"bp@suse.de" <bp@suse.de>,
	"jpoimboe@kernel.org" <jpoimboe@kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
	Peter Jonasson <pjonasson@vmware.com>,
	Yiu Cho Lau <lauyiuch@vmware.com>, Rajender M <manir@vmware.com>,
	Abdul Anshad Azeez <aazees@vmware.com>,
	"Kodeswaran Kumarasamy" <kkumarasamy@vmware.com>,
	Rahul Gopakumar <gopakumarr@vmware.com>
Subject: RE: Performance Regression in Linux Kernel 5.19
Date: Fri, 9 Sep 2022 21:22:12 +0000	[thread overview]
Message-ID: <3758868033fe49d5ba54e500e16df35f@AcuMS.aculab.com> (raw)
In-Reply-To: <PH0PR05MB8448A203A909959FAC754B7AAF439@PH0PR05MB8448.namprd05.prod.outlook.com>

From: Manikandan Jagatheesan
> Sent: 09 September 2022 12:46
> 
> As part of VMware's performance regression testing for Linux
> Kernel upstream releases, we have evaluated the performance
> of Linux kernel 5.19 against the 5.18 release and we have
> noticed performance regressions in Linux VMs on ESXi as shown
> below.
> - Compute(up to -70%)
> - Networking(up to -30%)
> - Storage(up to -13%)
> 
> After performing the bisect between kernel 5.18 and 5.19, we
> identified the root cause to be the enablement of IBRS mitigation
> for spectre_v2 vulnerability by commit 6ad0ad2bf8a6 ("x86/bugs:
> Report Intel retbleed vulnerability").

As a matter of interest how much faster does it go if you
boot with all mitigations disabled and compile without
retpolines and without page table separation?

There are plenty of semi-embedded systems (even running on x86)
where there are a limited set of binaries, it is difficult to
add new binaries, and everything basically runs as root.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  parent reply	other threads:[~2022-09-09 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 11:46 Manikandan Jagatheesan
2022-09-09 13:18 ` Peter Zijlstra
2022-09-09 21:22 ` David Laight [this message]
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
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=3758868033fe49d5ba54e500e16df35f@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=aazees@vmware.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --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

all inboxes | Powered by JetHome®