From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: bsegall@google.com
Cc: Yuyang Du <yuyang.du@intel.com>,
mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, pjt@google.com,
arjan.van.de.ven@intel.com, len.brown@intel.com,
rafael.j.wysocki@intel.com, alan.cox@intel.com,
mark.gross@intel.com, fengguang.wu@intel.com
Subject: Re: [PATCH 2/2 v2] sched: Rewrite per entity runnable load average tracking
Date: Wed, 16 Jul 2014 10:27:04 +0200 [thread overview]
Message-ID: <1405499224.5872.38.camel@marge.simpson.net> (raw)
In-Reply-To: <xm26pph6wmzy.fsf@sword-of-the-dawn.mtv.corp.google.com>
On Tue, 2014-07-15 at 10:27 -0700, bsegall@google.com wrote:
> It would still be good to see pipe_test numbers at various cgroup depths.
My t^Hcrusty ole box seems to be saying..
cgexec -g cpu:a pipe-test 1
3.16.0-default 5.016373 usecs/loop -- avg 5.021115 398.3 KHz
3.16.0-default+tim 5.003933 usecs/loop -- avg 4.986591 401.1 KHz
cgexec -g cpu:a/b pipe-test 1
3.16.0-default 5.543566 usecs/loop -- avg 5.565475 359.4 KHz
3.16.0-default+tim 5.663404 usecs/loop -- avg 5.647020 354.2 KHz
cgexec -g cpu:a/b/c pipe-test 1
3.16.0-default 6.092256 usecs/loop -- avg 6.094186 328.2 KHz
3.16.0-default+tim 6.311192 usecs/loop -- avg 6.299077 317.5 KHz
..that 0 KHz will become easier to achieve.
prev parent reply other threads:[~2014-07-16 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 23:15 [PATCH 0/2 " Yuyang Du
2014-07-13 23:15 ` [PATCH 1/2 v2] sched: Remove update_rq_runnable_avg Yuyang Du
2014-07-13 23:15 ` [PATCH 2/2 v2] sched: Rewrite per entity runnable load average tracking Yuyang Du
2014-07-14 19:33 ` bsegall
2014-07-15 1:51 ` Yuyang Du
2014-07-15 17:27 ` bsegall
2014-07-15 23:45 ` Yuyang Du
2014-07-16 8:27 ` Mike Galbraith [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=1405499224.5872.38.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=alan.cox@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=bsegall@google.com \
--cc=fengguang.wu@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome