From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Brendan Gregg <brendan.d.gregg@gmail.com>,
Jeff Merkey <linux.mdb@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC] The Linux Scheduler: a Decade of Wasted Cores Report
Date: Mon, 25 Apr 2016 11:18:45 +0200 [thread overview]
Message-ID: <1461575925.3670.25.camel@gmail.com> (raw)
In-Reply-To: <1461481517.3835.125.camel@gmail.com>
On Sun, 2016-04-24 at 09:05 +0200, Mike Galbraith wrote:
> On Sat, 2016-04-23 at 18:38 -0700, Brendan Gregg wrote:
>
> > The bugs they found seem real, and their analysis is great (although
> > using visualizations to find and fix scheduler bugs isn't new), and it
> > would be good to see these fixed. However, it would also be useful to
> > double check how widespread these issues really are. I suspect many on
> > this list can test these patches in different environments.
>
> Part of it sounded to me very much like they're meeting and "fixing"
> SMP group fairness...
Ew, NUMA boxen look like they could use a hug or two. Add a group of
one hog to compete with a box wide kbuild, ~lose a node.
Master.today, 4 node box, make -j 192 modules
root group
real 1m6.987s 1.00
cgroup vs 1 group of 1 hog
real 1m20.871s 1.20
cgroup vs 2 groups of 1 hog
real 1m48.803s 1.62
-Mike
next prev parent reply other threads:[~2016-04-25 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 18:20 [RFC] The Linux Scheduler: a Decade of Wasted Cores Report Jeff Merkey
2016-04-24 1:38 ` Brendan Gregg
2016-04-24 7:05 ` Mike Galbraith
2016-04-25 9:18 ` Mike Galbraith [this message]
2016-04-27 7:09 ` [patch] sched: Fix smp nice induced group scheduling load distribution woes Mike Galbraith
2016-04-28 9:11 ` Peter Zijlstra
2016-04-28 12:29 ` Mike Galbraith
2016-04-25 9:34 ` [RFC] The Linux Scheduler: a Decade of Wasted Cores Report Peter Zijlstra
2016-04-25 17:54 ` Rik van Riel
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=1461575925.3670.25.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=brendan.d.gregg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=peterz@infradead.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