From: Libo Chen <libo.chen@huawei.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: <tglx@linutronix.de>, <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Li Zefan" <lizefan@huawei.com>, <peterz@infradead.org>,
Huang Qiang <h.huangqiang@huawei.com>
Subject: Re: balance storm
Date: Wed, 28 May 2014 09:04:04 +0800 [thread overview]
Message-ID: <53853604.50500@huawei.com> (raw)
In-Reply-To: <1401196807.5134.132.camel@marge.simpson.net>
On 2014/5/27 21:20, Mike Galbraith wrote:
> On Tue, 2014-05-27 at 20:50 +0800, Libo Chen wrote:
>
>> in my box:
>>
>> perf top -g --sort=symbol
>>
>> Events: 3K cycles
>> 73.27% [k] read_hpet
>> 4.30% [k] _raw_spin_lock_irqsave
>> 1.88% [k] __schedule
>> 1.00% [k] idle_cpu
>> 0.91% [k] native_write_msr_safe
>> 0.68% [k] select_task_rq_fair
>> 0.51% [k] module_get_kallsym
>> 0.49% [.] sem_post
>> 0.44% [.] main
>> 0.41% [k] menu_select
>> 0.39% [k] _raw_spin_lock
>> 0.38% [k] __switch_to
>> 0.33% [k] _raw_spin_lock_irq
>> 0.32% [k] format_decode
>> 0.29% [.] usleep
>> 0.28% [.] symbols__insert
>> 0.27% [k] tick_nohz_stop_sched_tick
>> 0.27% [k] update_stats_wait_end
>> 0.26% [k] apic_timer_interrupt
>> 0.25% [k] enqueue_entity
>> 0.25% [k] sched_clock_local
>> 0.24% [k] _raw_spin_unlock_irqrestore
>> 0.24% [k] select_idle_sibling
>
> read_hpet? Are you booting box notsc or something? Migration cost is
> the least of your worries.
oh yes, no tsc only hpet in my box. I don't know hhy is read_hpet is hot.
but when I bind 3-th tasks to percpu,cost will be rapid decline, yet perf
shows read_hpet is still hot.
after bind
Events: 561K cycles
64.18% [kernel] [k] read_hpet
5.51% usleep [.] main
2.71% [kernel] [k] __schedule
1.82% [kernel] [k] _raw_spin_lock_irqsave
1.56% libc-2.11.3.so [.] usleep
1.07% [kernel] [k] apic_timer_interrupt
0.89% libc-2.11.3.so [.] __GI___libc_nanosleep
0.82% [kernel] [k] native_write_msr_safe
0.82% [kernel] [k] ktime_get
0.71% [kernel] [k] trace_hardirqs_off
0.63% [kernel] [k] __switch_to
0.60% [kernel] [k] _raw_spin_unlock_irqrestore
0.47% [kernel] [k] menu_select
0.46% [kernel] [k] _raw_spin_lock
0.45% [kernel] [k] enqueue_entity
0.45% [kernel] [k] sched_clock_local
0.43% [kernel] [k] try_to_wake_up
0.42% [kernel] [k] hrtimer_nanosleep
0.36% [kernel] [k] do_nanosleep
0.35% [kernel] [k] _raw_spin_lock_irq
0.34% [kernel] [k] rb_insert_color
0.29% [kernel] [k] update_curr
0.29% [kernel] [k] native_sched_clock
0.28% [kernel] [k] hrtimer_interrupt
0.28% [kernel] [k] rcu_idle_exit_common
0.27% [kernel] [k] hrtimer_init
0.27% [kernel] [k] __hrtimer_start_range_ns
0.26% [kernel] [k] __rb_erase_color
0.26% [kernel] [k] lock_hrtimer_base
0.25% [kernel] [k] trace_hardirqs_on
0.23% [kernel] [k] rcu_idle_enter_common
0.23% [kernel] [k] cpuidle_idle_call
0.23% [kernel] [k] finish_task_switch
0.22% [kernel] [k] set_next_entity
0.22% [kernel] [k] cpuacct_charge
0.22% [kernel] [k] pick_next_task_fair
0.21% [kernel] [k] sys_nanosleep
0.20% [kernel] [k] rb_next
0.20% [kernel] [k] start_critical_timings
>
> -Mike
>
>
>
next prev parent reply other threads:[~2014-05-28 1:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 3:04 balance storm Libo Chen
2014-05-26 5:11 ` Mike Galbraith
2014-05-26 12:16 ` Libo Chen
2014-05-26 14:19 ` Mike Galbraith
2014-05-27 7:56 ` Libo Chen
2014-05-27 9:55 ` Mike Galbraith
2014-05-27 12:50 ` Libo Chen
2014-05-27 13:20 ` Mike Galbraith
2014-05-28 1:04 ` Libo Chen [this message]
2014-05-28 1:53 ` Mike Galbraith
2014-05-28 6:54 ` Libo Chen
2014-05-28 8:16 ` Mike Galbraith
2014-05-28 9:08 ` Thomas Gleixner
2014-05-28 10:30 ` Peter Zijlstra
2014-05-28 10:52 ` Borislav Petkov
2014-05-28 11:43 ` Libo Chen
2014-05-28 11:55 ` Mike Galbraith
2014-05-29 7:58 ` Libo Chen
2014-05-29 7:57 ` Libo Chen
2014-05-27 20:53 ` Thomas Gleixner
2014-05-28 1:06 ` Libo Chen
2014-05-26 7:56 ` Mike Galbraith
2014-05-26 11:49 ` Libo Chen
2014-05-26 14:03 ` Mike Galbraith
2014-05-27 7:44 ` Libo Chen
2014-05-27 8:12 ` Mike Galbraith
2014-05-27 9:48 ` Peter Zijlstra
2014-05-27 10:05 ` Mike Galbraith
2014-05-27 10:43 ` Peter Zijlstra
2014-05-27 10:55 ` Mike Galbraith
2014-05-27 12:56 ` Libo Chen
2014-05-27 12:55 ` Libo Chen
2014-05-27 13:13 ` Peter Zijlstra
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=53853604.50500@huawei.com \
--to=libo.chen@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=h.huangqiang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@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