From owner-freebsd-net@FreeBSD.ORG Sun Dec 26 18:28:30 2010 Return-Path: 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 6EE9E106566C for ; Sun, 26 Dec 2010 18:28:30 +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 D66858FC13 for ; Sun, 26 Dec 2010 18:28:29 +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 oBQISQX8018877; Mon, 27 Dec 2010 00:28:27 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D17894A.1030809@rdtc.ru> Date: Mon, 27 Dec 2010 00:28:26 +0600 From: Eugene Grosbein 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: Gleb Kurtsou References: <4D0CFEFF.3000902@rdtc.ru> <20101226175322.GB45598@tops> In-Reply-To: <20101226175322.GB45598@tops> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2010 18:28:30 -0000 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 in each vlan. >> >> For lagg1, lagg distributes outgoing traffic over two ports just fine. >> For lagg0 (untagged ethernet segment with only 2 MAC addresses) >> less than 0.07% (54Mbit/s max) of traffic goes to em0 >> and over 99.92% goes to em1, that's bad. >> >> That's general traffic of several thousands of customers surfing the web, >> using torrents etc. I've glanced over lagg/lacp sources if src/sys/net/ >> and found nothing suspicious, it should extract and use srcIP/dstIP for hash. >> >> How do I debug this problem? > Could you try the patch attached. It changes hash function for > distributing traffic. I've already found source of this problem. That's not hash function problem (it works just fine when called), that's lagg(4) driver not using hashes for some workflows. Details can be found in this thread, as well as solution. Eugene Grosbein