From: Peter Zijlstra <peterz@infradead.org>
To: "Alexandre-Xavier Labonté-Lamoureux" <axdoomer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduler patches: 6x performance increase when system is under heavy load
Date: Tue, 20 Dec 2016 14:59:29 +0100 [thread overview]
Message-ID: <20161220135929.GP3124@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKTMqxtP7J+SJiQ-4B5ckcDMipY0kbY_DH-hyT=o0ZZghOvVzw@mail.gmail.com>
Sorry for the delay, got side-tracked for a bit..
On Wed, Dec 14, 2016 at 12:15:25AM -0500, Alexandre-Xavier Labonté-Lamoureux wrote:
> > Which of the 4 patches does this?
>
> I used all the 4 patches at the same time. Each patch fixes a
> different bug. Would you like me to try each of them individually?
Yes.
> Were you already aware of each of these bugs?
I had seen the paper and the patches. One of the issues has been fixed,
one is a non-issue and we had ideas about at least one other and I
cannot quite remember what the 4th was.
> > Also, what hypervisor are you using and what does the output of booting
> > with "sched_debug" look like?
>
> I was running the distro in VirualBox on Fedora. Here's the info from
> /proc/sched_debug:
> https://justpaste.it/11dhb
> dmesg: https://justpaste.it/11dhr
>
Ah, I meant dmesg with the "sched_debug" boot cmdline option (and
probably: "debug ignore_loglevel" added too) of the unmodified kernel.
> > Lastly, can you reproduce on real hardware?
>
> No. On real hardware, I tested in Ubuntu on an i7-4790 3.60GHz CPU
> without disabling HT and I saw no difference between CFS, the patched
> kernel and MuQSS. If I get to know a reason why one would be better
> than the other, I'd take the time to test it on more hardware. I'm
> curious how I got such a performance improvement in my VM.
OK, I'll also have to look at VirtualBox sources to see if they use
paravirt locking bits, not having support for that could make a
significant difference I suppose.
prev parent reply other threads:[~2016-12-20 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 21:41 Alexandre-Xavier Labonté-Lamoureux
2016-12-13 13:40 ` Peter Zijlstra
2016-12-14 5:15 ` Alexandre-Xavier Labonté-Lamoureux
2016-12-20 13:59 ` Peter Zijlstra [this message]
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=20161220135929.GP3124@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=axdoomer@gmail.com \
--cc=linux-kernel@vger.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
Powered by JetHome