FW: Estimated speed/duplex values for virtual NICs
Based on packet delivery being a memory-to-memory operation with diag2a8, I'm leaning toward just inserting an estimated value of 10Gbit/sec per interface for the speed estimate reported by dladm. Does anyone else have a better value or an idea of how to measure this value? Further, does VSWITCH support generating BCI (backward congestion indicator) frames? If so, I'll just hard-code the media speed value at 100Gbit and enable the BCI support in the OpenSolaris stack and let it negotiate down.
Re: FW: Estimated speed/duplex values for virtual NICs
On Monday, 03/09/2009 at 12:09 EDT, David Boyes dbo...@sinenomine.net wrote: Further, does VSWITCH support generating BCI (backward congestion indicator) frames? Never heard of it. Whatever they are, the VSWITCH doesn't generate them or cause them to be generated. Alan Altmark z/VM Development IBM Endicott
Re: FW: Estimated speed/duplex values for virtual NICs
FWIW, The channel bonding stuff (SuSE 10) seems to also care about speed/duplex values and can't get them from a dedicated OSA either. It complains and goes on its merry way: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full Marcy