From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Yong Zhang <yong.zhang0@gmail.com>,
Carl-Johan Kjellander <carl-johan@klarna.com>,
linux-kernel@vger.kernel.org
Subject: Re: Sched_autogroup and niced processes
Date: Fri, 13 May 2011 15:13:26 +0200 [thread overview]
Message-ID: <1305292406.27263.20.camel@marge.simson.net> (raw)
In-Reply-To: <20110513100411.GA21022@elte.hu>
On Fri, 2011-05-13 at 12:04 +0200, Ingo Molnar wrote:
> Still, the other important problem is that we still seem to have a bug, even
> with the cgroup set to low prio seti@home is sucking up CPU resources ...
I don't see how. Other than the expected nice 19 overrun when nice 0
group blocks, it works fine on my little Q6600 box.
time make -j4 vmlinux (cache hot)
real 2m22.996s
user 7m6.887s
sys 0m48.999s
echo 0 > sched_autogroup_enabled
time make -j4 vmlinux
real 2m17.052s (darn, no free lunch)
user 7m5.483s
sys 0m49.415s
echo 1 > sched_autogroup_enabled
simultaneous massive_intr 8 9999 in nice 19 autogroup and
time make -j4 vmlinux in a nice 0 autogroup
real 2m30.863s
user 7m5.363s
sys 0m47.359s
142.996/150.863 = .947 (a tad low)
repeat with 2 kbuild tasks/core to cut nice 0 group's idle time
time make -j8 vmlinux
real 2m24.925s
user 7m16.327s
sys 0m50.807s
142.996/144.925 = .986 (all better)
-Mike
next prev parent reply other threads:[~2011-05-13 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 7:39 Sched_autogroup and niced processes Carl-Johan Kjellander
2011-05-13 7:53 ` Yong Zhang
2011-05-13 8:05 ` Mike Galbraith
2011-05-13 8:22 ` Ingo Molnar
2011-05-13 8:41 ` Peter Zijlstra
2011-05-13 9:05 ` Ingo Molnar
2011-05-13 9:07 ` Peter Zijlstra
2011-05-13 9:14 ` Carl-Johan Kjellander
2011-05-13 9:29 ` Ingo Molnar
2011-05-13 9:46 ` Peter Zijlstra
2011-05-13 10:04 ` Ingo Molnar
2011-05-13 13:13 ` Mike Galbraith [this message]
2011-05-13 13:24 ` Peter Zijlstra
2011-05-13 13:36 ` Carl-Johan Kjellander
2011-05-13 14:06 ` 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=1305292406.27263.20.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=carl-johan@klarna.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@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