From: David Laight <David.Laight@ACULAB.COM>
To: 'Bernd Petrovitsch' <bernd@petrovitsch.priv.at>,
Muni Sekhar <munisekharrms@gmail.com>
Cc: peter enderborg <peter.enderborg@sony.com>,
Greg KH <greg@kroah.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: RE: Scheduler benchmarks
Date: Wed, 19 Aug 2020 14:36:25 +0000 [thread overview]
Message-ID: <e8acd1a8444846b196d5fa1fe45806bb@AcuMS.aculab.com> (raw)
In-Reply-To: <4a20a4bb-0bc7-edb1-bd27-217d8dafe87c@petrovitsch.priv.at>
From: Bernd Petrovitsch
> Sent: 19 August 2020 11:22
>
> On 19/08/2020 10:16, Muni Sekhar wrote:
> > On Tue, Aug 18, 2020 at 11:45 PM peter enderborg
> > <peter.enderborg@sony.com> wrote:
> [...]
> >> On the 4.4 kernel you dont have
> >>
> >> +CONFIG_RETPOLINE=y
> >> +CONFIG_INTEL_RDT=y
> > Thanks! That is helpful. Yes, I see 4.4 kernel don't have the above
> > two config options.
> > What analysis can be done to narrow down the root cause?
> > Any example of reference could be helpful to understand.
>
> I haven't checked the date of the older kernel but Spectre+
> Meltdown mitigation costs a lot (20%-30% speed IIRC, out
> of the top of my head).
It depends greatly on the benchmark.
Page table separation has a massive effect on anything that
does a lot of short system calls.
There may be some mitigation in very recent hardware.
And I can't remember if it gets disabled for 'root' processes
(which can read kernel memory anyway).
It is definitely worth building a kernel with the mitigations
disabled - if only to check that they are responsible.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-08-19 14:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:30 Scheduler benchmarks Muni Sekhar
2020-08-18 14:36 ` Greg KH
2020-08-18 16:01 ` Muni Sekhar
2020-08-18 16:50 ` Muni Sekhar
2020-08-18 16:54 ` Muni Sekhar
2020-08-18 17:14 ` Greg KH
2020-08-18 17:31 ` Muni Sekhar
2020-08-18 17:36 ` Greg KH
2020-08-18 17:53 ` Muni Sekhar
2020-08-18 18:15 ` peter enderborg
2020-08-19 10:16 ` Muni Sekhar
2020-08-19 10:21 ` Bernd Petrovitsch
2020-08-19 14:36 ` David Laight [this message]
2020-08-19 10:42 ` Greg KH
2020-08-19 16:43 ` Valdis Klētnieks
2020-08-19 16:47 ` Greg KH
2021-04-29 21:32 ` Arnaldo Carvalho de Melo
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=e8acd1a8444846b196d5fa1fe45806bb@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bernd@petrovitsch.priv.at \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=peter.enderborg@sony.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 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).