From: peter enderborg <peter.enderborg@sony.com>
To: Muni Sekhar <munisekharrms@gmail.com>, Greg KH <greg@kroah.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Subject: Re: Scheduler benchmarks
Date: Tue, 18 Aug 2020 20:15:26 +0200 [thread overview]
Message-ID: <84362b8b-971f-fb89-115d-41d2457c24fd@sony.com> (raw)
In-Reply-To: <CAHhAz+hi9rh5w8hNyas0RkO4WwZXsSNh5g0nS710NSr6-ntioQ@mail.gmail.com>
On 8/18/20 7:53 PM, Muni Sekhar wrote:
> On Tue, Aug 18, 2020 at 11:06 PM Greg KH <greg@kroah.com> wrote:
>> On Tue, Aug 18, 2020 at 11:01:35PM +0530, Muni Sekhar wrote:
>>> On Tue, Aug 18, 2020 at 10:44 PM Greg KH <greg@kroah.com> wrote:
>>>> On Tue, Aug 18, 2020 at 10:24:13PM +0530, Muni Sekhar wrote:
>>>>> On Tue, Aug 18, 2020 at 8:06 PM Greg KH <greg@kroah.com> wrote:
>>>>>> On Tue, Aug 18, 2020 at 08:00:11PM +0530, Muni Sekhar wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I’ve two identical Linux systems with only kernel differences.
>>>>>> What are the differences in the kernels?
>>>> You didn't answer this question, is this the same kernel source being
>>>> compared here? Same version? Same compiler? Everything identical?
>>> Both systems are having exactly the same hardware configuration.
>>> Compiler and kernel versions are different. One system has Ubuntu
>>> 16.04.4 LTS(4.4.0-66-generic kernel with gcc version 5.4.0) kernel and
>>> the other one has Ubuntu 18.04.4 LTS(4.15.0-91-generic kernel with gcc
>>> version 7.5.0).
>> Those are _very_ different kernel versions, with many years and tens of
>> thousands of different changes between them.
>>
>> Hopefully the newer kernel is faster, so just stick with that :)
> But unfortunately the newer kernel is very slow, that is the reason
> for starting this investigation :)
> Any type of help, and guidelines to dive deeper will be highly appreciated.
On the 4.4 kernel you dont have
+CONFIG_RETPOLINE=y
+CONFIG_INTEL_RDT=y
And your base is very different two.
Try to use mainline on both system and see.
You can also use the same base kernel version from ubuntu and
run your test.
>> greg k-h
>
>
next prev parent reply other threads:[~2020-08-18 18:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:30 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 [this message]
2020-08-19 10:16 ` Muni Sekhar
2020-08-19 10:21 ` Bernd Petrovitsch
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=84362b8b-971f-fb89-115d-41d2457c24fd@sony.com \
--to=peter.enderborg@sony.com \
--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 \
/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®