Thanks,Cathy.
Didn't regonize the issue lies in there

Regards,
Zhijun
Cathy Zhou wrote:
> See bug 6551885.
>
> Like described in the bug report, this is because running this 
> commands requires devinfo to take a snapshot of all the devices.
>
> This should be able to be fixed as part of the Clearview UV component, 
> because "dladm show-link" will query dlmgmtd instead of devinfo of the 
> list of links.
>
> - Cathy
>
>
>> Hi folks,
>>
>> I just happened to find that dladm show-link takes a longer time than I
>> expected to finish. Truss results can explain a bit,but I think perhaps
>> 4 seconds is a little long,and I am wondering whether there are spaces
>> to optimize the time it takes.
>>
>>
>> Thanks,
>> Zhijun
>>
>> -----------------------------------------------------------------------------------------------
>>  
>>
>> bash-3.00# uname -a
>> SunOS iniquity 5.11 snv_68 i86pc i386 i86pc
>>
>> bash-3.00# mpstat
>> CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
>> 0 4 0 0 351 248 99 0 4 0 0 19 0 0 0 100
>> 1 3 0 0 43 1 84 0 4 0 0 57 0 0 0 100
>>
>>
>> bash-3.00# time dladm show-link
>> bge0 type: non-vlan mtu: 1500 device: bge0
>> bge1 type: non-vlan mtu: 1500 device: bge1
>> e1000g0 type: non-vlan mtu: 1500 device: e1000g0
>> e1000g1 type: non-vlan mtu: 1500 device: e1000g1
>> e1000g2 type: non-vlan mtu: 1500 device: e1000g2
>> e1000g3 type: non-vlan mtu: 1500 device: e1000g3
>>
>> real 0m4.174s
>> user 0m0.003s
>> sys 0m4.168s
>>
>> bash-3.00# time dladm show-dev
>> bge0 link: up speed: 100Mb duplex: full
>> bge1 link: down speed: 0Mb duplex: unknown
>> e1000g0 link: up speed: 1000Mb duplex: full
>> e1000g1 link: unknown speed: 0Mb duplex: half
>> e1000g2 link: unknown speed: 0Mb duplex: half
>> e1000g3 link: unknown speed: 0Mb duplex: half
>>
>> real 0m0.045s
>> user 0m0.010s
>> sys 0m0.034s
>>
>> _______________________________________________
>> networking-discuss mailing list
>> [email protected]
>

_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to