Now cpu7 has most of the interrupt (delete other cpu stats as they are 0).
so why the execname is sched when interrupt happens?
device | cpu0 %tim cpu1 %tim cpu2 %tim cpu3
%tim cpu4 %tim cpu5 %tim cpu6 %tim cpu7 %tim
------------+--------------------------------------------------------------------------------------------------------------------------
ehci#0 | 0 0.0 0 0.0 0 0.0 0
0.0 0 0.0 2 0.0 0 0.0 0 0.0
nge#0 | 0 0.0 0 0.0 0 0.0 0
0.0 0 0.0 0 0.0 0 0.0 6260 2.9
nge#1 | 0 0.0 0 0.0 0 0.0 0
0.0 0 0.0 0 0.0 0 0.0 2 0.0
nv_sata#0 | 0 0.0 0 0.0 0 0.0 0
0.0 0 0.0 2 0.0 0 0.0 0 0.0
nv_sata#2 | 0 0.0 0 0.0 0 0.0 0
0.0 0 0.0 0 0.0 0 0.0 6260 0.5
On Thu, Jan 21, 2010 at 6:54 PM, Michael Schuster
<michael.schus...@sun.com>wrote:
> Qihua Wu wrote:
>
>> Why sched is often interrupt on cpu 0 instead of distribution evenly on
>> all cpu?
>>
>> dtrace -n 'sdt:::interrupt-start { @num[execname,cpu] = count(); }'
>> dtrace: description 'sdt:::interrupt-start ' matched 1 probe
>>
>
> the output of intrstat may help.
>
> Michael
> --
> Michael Schuster http://blogs.sun.com/recursion
> Recursion, n.: see 'Recursion'
>
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
