public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex,Shi" <alex.shi@intel.com>
To: Nikhil Rao <ncrao@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"Chen, Tim C" <tim.c.chen@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: power increase issue on light load
Date: Wed, 29 Jun 2011 14:55:46 +0800	[thread overview]
Message-ID: <1309330546.14604.97.camel@debian> (raw)
In-Reply-To: <1309317764.14604.92.camel@debian>

On Wed, 2011-06-29 at 11:22 +0800, Alex,Shi wrote:
> > 
> > Looking at the schedstat data Alex posted:
> > - Distribution of load balances across cores looks about the same.
> > - Load balancer does more idle balances on 3.0-rc4 as compared to
> > 2.6.39 on SMT and NUMA domains. Busy and newidle balances are a mixed
> > bag.
> > - I see far fewer affine wakeups on 3.0-rc4 as compared to 2.6.39.
> > About half as many affine wakeups on SMT and about a quarter as many
> > on NUMA.
> > 
> > I'm investigating the impact of the load resolution patchset on
> > effective load and wake affine calculations. This seems to be the most
> > obvious difference from the schedstat data.
> > 
> > Alex -- I have a couple of questions about your test setup and results.
> > - What is the impact on throughput of these benchmarks?
> 
> both on bltk-office and light load specpower, 10%/20%/30% load, the
> throughput almost have no change on my NHM-EP server and t410 laptop.
> > - Would it be possible to get a "perf sched" trace on these two kernels?

I tried the 'perf sched record' and then 'perf sched trace' as usage
show. but in fact, the 'perf sched' doesn't support 'trace' command now.
since the 'perf sched record' is using 'perf record -e sched:xxx' to do
record. I used 'perf record' directly. The follow info collected in 300'
on my NHM-EP for benchmark bltk-office. 

[alexs@lkp-ne01 ~]$ grep -e Events.*sched
linux-2.6/perf-report-3.0.0-rc5  
# Events: 11K sched:sched_wakeup
# Events: 1K sched:sched_wakeup_new
# Events: 24K sched:sched_switch
# Events: 3K sched:sched_migrate_task
# Events: 851  sched:sched_process_free
# Events: 1K sched:sched_process_exit
# Events: 1K sched:sched_process_wait
# Events: 1K sched:sched_process_fork
# Events: 12K sched:sched_stat_wait
# Events: 9K sched:sched_stat_sleep
# Events: 452  sched:sched_stat_iowait
# Events: 16K sched:sched_stat_runtime
[alexs@lkp-ne01 ~]$ 
[alexs@lkp-ne01 ~]$ 
[alexs@lkp-ne01 ~]$ grep -e
Events.*sched /mnt/linux-2.6.39/perf-report-2.6.39 
# Events: 5K sched:sched_wakeup
# Events: 615  sched:sched_wakeup_new
# Events: 11K sched:sched_switch
# Events: 2K sched:sched_migrate_task
# Events: 541  sched:sched_process_free
# Events: 692  sched:sched_process_exit
# Events: 1K sched:sched_process_wait
# Events: 615  sched:sched_process_fork
# Events: 6K sched:sched_stat_wait
# Events: 4K sched:sched_stat_sleep
# Events: 178  sched:sched_stat_iowait
# Events: 9K sched:sched_stat_runtime



  reply	other threads:[~2011-06-29  6:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  2:43 power increase issue on light load Alex,Shi
2011-06-23  9:02 ` Peter Zijlstra
2011-06-24  0:41   ` Alex,Shi
2011-06-28  0:02     ` Alex,Shi
2011-06-28 14:59       ` Peter Zijlstra
2011-06-28 17:13         ` Nikhil Rao
2011-06-29  2:30           ` Nikhil Rao
2011-06-29  3:22             ` Alex,Shi
2011-06-29  6:55               ` Alex,Shi [this message]
2011-06-30  0:26                 ` Nikhil Rao
2011-06-30  8:38                   ` Alex,Shi
2011-06-30  0:07             ` Nikhil Rao
2011-06-30  8:34               ` Alex,Shi
2011-07-01  5:44 ` Ming Lei
2011-07-01 18:00   ` Nikhil Rao
2011-07-01 23:51     ` Ming Lei
2011-07-04  0:45     ` Alex,Shi

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=1309330546.14604.97.camel@debian \
    --to=alex.shi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ncrao@google.com \
    --cc=peterz@infradead.org \
    --cc=shaohua.li@intel.com \
    --cc=tim.c.chen@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