On 14 May 2018 at 15:03, Vinícius Ferrão <fer...@if.ufrj.br> wrote:
> You should use better hashing algorithms for LACP. > > Take a look at this explanation: https://www.ibm.com/ > developerworks/community/blogs/storageneers/entry/Enhancing_IP_Network_ > Performance_with_LACP?lang=en > > In general only L2 hashing is made, you can achieve better throughput with > L3 and multiple IPs, or with L4 (ports). > > Your switch should support those features too, if you’re using one. > > V. > The problem isn't the LACP connection between the host & the switch, but setting up LACP between the VM & the host. For reasons of stability, my 4.1 cluster's switch type is currently "Linux Bridge", not "OVS". Ergo my question, is LACP on the VM possible with that, or will I have to use ALB? Regards, Doug > > > On 14 May 2018, at 15:16, Doug Ingham wrote: > > Hi All, > My hosts have all of their interfaces bonded via LACP to maximise > throughput, however the VMs are still limited to Gbit virtual interfaces. > Is there a way to configure my VMs to take full advantage of the bonded > physical interfaces? > > One way might be adding several VIFs to each VM & using ALB bonding, > however I'd rather use LACP if possible... > > Cheers, > -- > Doug > > -- Doug
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org
