From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: 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-perf-users@vger.kernel.org
Subject: Re: Scheduler benchmarks
Date: Wed, 19 Aug 2020 10:21:50 +0000 [thread overview]
Message-ID: <4a20a4bb-0bc7-edb1-bd27-217d8dafe87c@petrovitsch.priv.at> (raw)
In-Reply-To: <CAHhAz+iC_F5w5EoZP8-dBNm+DV0uNMva6Mr2uBdmZtejL1OH-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
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).
MfG,
Bernd
--
There is no cloud, just other people computers.
-- https://static.fsf.org/nosvn/stickers/thereisnocloud.svg
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3161 bytes --]
next prev parent reply other threads:[~2020-08-19 11:03 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 [this message]
2020-08-19 14:36 ` David Laight
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=4a20a4bb-0bc7-edb1-bd27-217d8dafe87c@petrovitsch.priv.at \
--to=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).