From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Yuyang Du <yuyang.du@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched/fair: Use instantaneous load in wakeup paths
Date: Fri, 17 Jun 2016 08:21:02 +0200 [thread overview]
Message-ID: <1466144462.3223.102.camel@gmail.com> (raw)
In-Reply-To: <1466080888.2278.30.camel@gmail.com>
Here are some schbench runs on an 8x8 box to show that longish
run/sleep period corner I mentioned.
vogelweide:~/:[1]# for i in `seq 5`; do schbench -m 8 -t 1 -a -r 10 2>&1 | grep 'threads 8'; done
cputime 30000 threads 8 p99 68
cputime 30000 threads 8 p99 46
cputime 30000 threads 8 p99 46
cputime 30000 threads 8 p99 45
cputime 30000 threads 8 p99 49
vogelweide:~/:[0]# echo NO_WAKE_INSTANTANEOUS_LOAD > /sys/kernel/debug/sched_features
vogelweide:~/:[0]# for i in `seq 5`; do schbench -m 8 -t 1 -a -r 10 2>&1 | grep 'threads 8'; done
cputime 30000 threads 8 p99 9968
cputime 30000 threads 8 p99 10224
vogelweide:~/:[0]#
Using instantaneous load, we fill the box every time, without, we stack
every time. This was with Peter's select_idle_sibling() rewrite
applied as well, but you can see that it does matter.
That doesn't mean I think my patch should immediately fly upstream
'course, who knows, there may be a less messy way to deal with it, or,
as already stated, maybe it just doesn't matter enough to the real
world to even bother with.
-Mike
next prev parent reply other threads:[~2016-06-17 6:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:58 [rfc patch] sched/fair: Use instantaneous load for fork/exec balancing Mike Galbraith
2016-06-14 14:14 ` Dietmar Eggemann
2016-06-14 16:40 ` Mike Galbraith
2016-06-15 15:32 ` Dietmar Eggemann
2016-06-15 16:03 ` Mike Galbraith
2016-06-15 19:03 ` Dietmar Eggemann
2016-06-16 3:33 ` Mike Galbraith
2016-06-16 9:01 ` Dietmar Eggemann
2016-07-04 15:04 ` Matt Fleming
2016-07-04 17:43 ` Mike Galbraith
2016-07-06 11:45 ` Matt Fleming
2016-07-06 12:21 ` Mike Galbraith
2016-07-11 8:58 ` Dietmar Eggemann
2016-07-12 11:14 ` Matt Fleming
2016-06-14 22:42 ` Yuyang Du
2016-06-15 7:01 ` Mike Galbraith
2016-06-16 11:46 ` [patch] sched/fair: Use instantaneous load in wakeup paths Mike Galbraith
2016-06-16 12:04 ` Mike Galbraith
2016-06-16 12:41 ` Mike Galbraith
2016-06-17 6:21 ` Mike Galbraith [this message]
2016-06-17 10:55 ` Dietmar Eggemann
2016-06-17 13:57 ` Mike Galbraith
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=1466144462.3223.102.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=yuyang.du@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.