From owner-freebsd-net@FreeBSD.ORG  Tue Dec 21 14:48:33 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 632DC106566B
	for <net@freebsd.org>; Tue, 21 Dec 2010 14:48:33 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from grosbein.pp.ru (grosbein.pp.ru [89.189.172.146])
	by mx1.freebsd.org (Postfix) with ESMTP id 2F9D88FC0C
	for <net@freebsd.org>; Tue, 21 Dec 2010 14:48:31 +0000 (UTC)
Received: from grosbein.pp.ru (localhost [127.0.0.1])
	by grosbein.pp.ru (8.14.4/8.14.4) with ESMTP id oBLEmUvs002180;
	Tue, 21 Dec 2010 20:48:30 +0600 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4D10BE3E.6030506@rdtc.ru>
Date: Tue, 21 Dec 2010 20:48:30 +0600
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4
MIME-Version: 1.0
To: Fabien Thomas <fabien.thomas@netasq.com>
References: <4D0CFEFF.3000902@rdtc.ru>
	<1292844095.1917.136.camel@stormi>	<4D1083D6.6010707@rdtc.ru>	<84530C06-AC2E-4E2B-BFD4-693902BB0FA6@netasq.com>	<4D10B2F4.1060404@rdtc.ru>
	<90F64F73-F9A8-4FD6-9303-2FC0D3424751@netasq.com>
In-Reply-To: <90F64F73-F9A8-4FD6-9303-2FC0D3424751@netasq.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Cc: net@freebsd.org
Subject: Re: lagg/lacp poor traffic distribution
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2010 14:48:33 -0000

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 show the queue (intr for the queue) normally it's the number of CPU available.

# vmstat -i
interrupt                          total       rate
irq5: uart2                            8          0
irq18: ehci0 uhci5+                    2          0
irq19: uhci2 uhci4+                 2182          0
irq23: uhci3 ehci1                   124          0
cpu0: timer                     39576224       1993
irq256: em0:rx 0               115571349       5822
irq257: em0:tx 0               136632905       6883
irq259: em1:rx 0               115829181       5835
irq260: em1:tx 0               138838991       6994
irq262: igb0:que 0             157354922       7927
irq263: igb0:que 1                577369         29
irq264: igb0:que 2                280207         14
irq265: igb0:que 3                241826         12
irq266: igb0:link                      2          0
irq267: igb1:que 0             164620363       8293
irq268: igb1:que 1                238678         12
irq269: igb1:que 2                248478         12
irq270: igb1:que 3                762453         38
irq271: igb1:link                      3          0
cpu2: timer                     39576052       1993
cpu3: timer                     39576095       1993
cpu1: timer                     39575913       1993
Total                          989503327      49849

It seems I have four queues per igb card but only one of them works?

Eugene Grosbein