Re: lagg/lacp poor traffic distribution

2010-12-26 Thread Eugene Grosbein
On 26.12.2010 23:53, Gleb Kurtsou wrote: >> I've loaded router using two lagg interfaces in LACP mode. >> lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. >> lagg1 has no IP address and has two ports (igb0 and igb1) and carry >> about 1000 dot-q vlans with lots of hosts

Re: lagg/lacp poor traffic distribution

2010-12-26 Thread Gleb Kurtsou
On (19/12/2010 00:35), Eugene Grosbein wrote: > Hi! > > I've loaded router using two lagg interfaces in LACP mode. > lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. > lagg1 has no IP address and has two ports (igb0 and igb1) and carry > about 1000 dot-q vlans with lots

Re: lagg/lacp poor traffic distribution

2010-12-25 Thread Ivan Voras
On 22.12.2010 18:55, Eugene Grosbein wrote: > It seems, we really need sysctl disabling lagg's use of flows, don't we? If no developer is willing to work on it right now, you should probably create a PR with your patch so it doesn't get lost. Also, a patch describing the sysctl in the lagg(4) ma

Re: lagg/lacp poor traffic distribution

2010-12-24 Thread Eugene Grosbein
On 24.12.2010 21:41, Shtorm wrote: > Sorry, I have no idea how to create nice diff, maybe point to small > howto will help :) Copy original file as "file.c.orig" and put your changes to "file.c" then do "diff -u file.c.orig file.c > file.c.diff" then repost file.c.diff contents.

Re: lagg/lacp poor traffic distribution

2010-12-24 Thread Shtorm
On Tue, 2010-12-21 at 16:39 +0600, Eugene Grosbein wrote: > On 20.12.2010 17:21, Shtorm wrote: > > On Sun, 2010-12-19 at 00:35 +0600, Eugene Grosbein wrote: > >> Hi! > >> > >> I've loaded router using two lagg interfaces in LACP mode. > >> lagg0 has IP address and two ports (em0 and em1) and carry

Re: lagg/lacp poor traffic distribution

2010-12-23 Thread Fabien Thomas
On Dec 22, 2010, at 6:55 PM, Eugene Grosbein wrote: > On 21.12.2010 21:57, Fabien Thomas wrote: > >>> irq262: igb0:que 0 157354922 7927 >>> irq263: igb0:que 1577369 29 >>> irq264: igb0:que 2280207 14 >>> irq265: igb0:que 3

Re: lagg/lacp poor traffic distribution

2010-12-22 Thread Eugene Grosbein
On 21.12.2010 21:57, Fabien Thomas wrote: >> irq262: igb0:que 0 157354922 7927 >> irq263: igb0:que 1577369 29 >> irq264: igb0:que 2280207 14 >> irq265: igb0:que 3241826 12 >> irq266: igb0:link

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Eugene Grosbein
On 21.12.2010 21:57, Fabien Thomas wrote: >> 1. Is it a bug or design problem? > > How many queues have you with igb? If it's one it will explain why the > flowid is bad for load balancing with lagg. How do I know? I've read igb(4) manual page and found no words >>> vmst

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Fabien Thomas
On Dec 21, 2010, at 3:48 PM, Eugene Grosbein wrote: > On 21.12.2010 20:41, Fabien Thomas wrote: > > 1. Is it a bug or design problem? How many queues have you with igb? If it's one it will explain why the flowid is bad for load balancing with lagg. >>> >>> How do I know? I'

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Eugene Grosbein
On 21.12.2010 20:41, Fabien Thomas wrote: 1. Is it a bug or design problem? >>> >>> How many queues have you with igb? If it's one it will explain why the >>> flowid is bad for load balancing with lagg. >> >> How do I know? I've read igb(4) manual page and found no words > vmstat -i will sho

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Fabien Thomas
On Dec 21, 2010, at 3:00 PM, Eugene Grosbein wrote: > On 21.12.2010 19:11, Fabien Thomas wrote: > I had this problem with igb driver, and I found, that lagg selects outgoing interface based on packet header flowid field if M_FLOWID field is set. And in the igb driver code flowid i

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Eugene Grosbein
On 21.12.2010 19:11, Fabien Thomas wrote: >>> I had this problem with igb driver, and I found, that lagg selects >>> outgoing interface based on packet header flowid field if M_FLOWID field >>> is set. And in the igb driver code flowid is set as >>> >>> #if __FreeBSD_version >= 80 >>> <--

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Fabien Thomas
>>> Hi! >>> >>> I've loaded router using two lagg interfaces in LACP mode. >>> lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. >>> lagg1 has no IP address and has two ports (igb0 and igb1) and carry >>> about 1000 dot-q vlans with lots of hosts in each vlan. >>> >>> Fo

Re: lagg/lacp poor traffic distribution

2010-12-21 Thread Eugene Grosbein
On 20.12.2010 17:21, Shtorm wrote: > On Sun, 2010-12-19 at 00:35 +0600, Eugene Grosbein wrote: >> Hi! >> >> I've loaded router using two lagg interfaces in LACP mode. >> lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. >> lagg1 has no IP address and has two ports (igb0 an

Re: lagg/lacp poor traffic distribution

2010-12-20 Thread Eugene Grosbein
On 21.12.2010 13:32, Eugene Grosbein wrote: >> I had this problem with igb driver, and I found, that lagg selects >> outgoing interface based on packet header flowid field if M_FLOWID field >> is set. And in the igb driver code flowid is set as >> >> #if __FreeBSD_version >= 80 >> <--><--

Re: lagg/lacp poor traffic distribution

2010-12-20 Thread Eugene Grosbein
On 20.12.2010 17:21, Shtorm wrote: > I had this problem with igb driver, and I found, that lagg selects > outgoing interface based on packet header flowid field if M_FLOWID field > is set. And in the igb driver code flowid is set as > > #if __FreeBSD_version >= 80 > <--><--><-->r

Re: lagg/lacp poor traffic distribution

2010-12-20 Thread Eugene Grosbein
On 20.12.2010 17:21, Shtorm wrote: > I had this problem with igb driver, and I found, that lagg selects > outgoing interface based on packet header flowid field if M_FLOWID field > is set. And in the igb driver code flowid is set as > > #if __FreeBSD_version >= 80 > <--><--><-->r

Re: lagg/lacp poor traffic distribution

2010-12-20 Thread Shtorm
On Sun, 2010-12-19 at 00:35 +0600, Eugene Grosbein wrote: > Hi! > > I've loaded router using two lagg interfaces in LACP mode. > lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. > lagg1 has no IP address and has two ports (igb0 and igb1) and carry > about 1000 dot-q vlan

Re: lagg/lacp poor traffic distribution

2010-12-18 Thread Julian Elischer
On 12/18/10 10:35 AM, Eugene Grosbein wrote: Hi! I've loaded router using two lagg interfaces in LACP mode. lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. lagg1 has no IP address and has two ports (igb0 and igb1) and carry about 1000 dot-q vlans with lots of hosts in

Re: lagg/lacp poor traffic distribution

2010-12-18 Thread Eugene Grosbein
On 19.12.2010 01:31, Thomas Donnelly wrote: > Check the load balancing algorithm on both sides. I usually balance on > src+dst mac. I'm only talking on traffic outgoing from FreeBSD host. Here it needs to be balanced using layer-3 src/dst addresses because src and dst macs are constant here.

Re: lagg/lacp poor traffic distribution

2010-12-18 Thread Thomas Donnelly
On Dec 18, 2010, at 12:35 PM, Eugene Grosbein wrote: > Hi! > > I've loaded router using two lagg interfaces in LACP mode. > lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. > lagg1 has no IP address and has two ports (igb0 and igb1) and carry > about 1000 dot-q vlans

Re: lagg/lacp poor traffic distribution

2010-12-18 Thread Eugene Grosbein
On 19.12.2010 00:35, Eugene Grosbein wrote: > Hi! > > I've loaded router using two lagg interfaces in LACP mode. > lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. > lagg1 has no IP address and has two ports (igb0 and igb1) and carry > about 1000 dot-q vlans with lots of

lagg/lacp poor traffic distribution

2010-12-18 Thread Eugene Grosbein
Hi! I've loaded router using two lagg interfaces in LACP mode. lagg0 has IP address and two ports (em0 and em1) and carry untagged frames. lagg1 has no IP address and has two ports (igb0 and igb1) and carry about 1000 dot-q vlans with lots of hosts in each vlan. For lagg1, lagg distributes outgoi