[Adding back the discuss@ mailing list.]

The "bond_mode" determines how traffic is balanced across interfaces.  The 
ovs-vswitchd.conf.db (5) man page contains a lot more information about how 
bonding works and can be configured.

--Justin


On Apr 6, 2012, at 4:31 AM, Folay_Chen wrote:

> Thanks for your reply!! You are right!!
> I created multiple iperf flows, some of them did use one link and the
> others did use another link!! But I can only feel this by creating
> enough flows. If just 2 flows were created, they usually just shared the
> same link, that is, the first couple of flows will be compressed into a
> single link while another link being kept idle (Ideally, the second flow
> should be immediately allocated to the idle link to achieve balance). I
> don't know the timing, when will OVS allocate a flow to another link? 
> 
> OVS can't distribute packets of the same flow to different interfaces.
> OVS can't really achieve balance/fairness between flows.
> OVS can't dynamically switch a flow between different interfaces on the
> fly based on the bandwidth utilization.
> 
> So it means the LACP implemented in OVS is not mature?
> Or it's just the nature of LACP? It needs extra QoS scheme to achieve
> real balance and full bandwidth utilization?
> 
> PS: One interesting thing:
> 
> In the very first sec (0.0~1.0sec), a flow can actually use the full
> bandwidth (20Mbps)!! And degraded to a single link bandwidth afterward
> (10Mbps)...
> 
> On Fri, 2012-04-06 at 01:46 -0700, Justin Pettit wrote:
>> On Apr 6, 2012, at 12:45 AM, Folay_Chen wrote:
>> 
>>> Once again, I test the bandwidth, the speed stays at 10Mbps...
>>> I expected that the speed should be doubled: 20Mbps.
>>> Any ideas?
>> 
>> Are you just doing a single iperf flow?  I'm not an export on LACP, but I 
>> suspect a single flow will only use one of the interfaces, since at best it 
>> can hash on L4 ports (i.e., it won't spread a single flow across multiple 
>> links).  Does it work as you expect if you run multiple iperf clients?
>> 
>> --Justin
>> 
>> 
> 

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to