From owner-freebsd-net@FreeBSD.ORG Tue Mar 17 18:33:54 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9164312 for ; Tue, 17 Mar 2015 18:33:54 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 374E76CA for ; Tue, 17 Mar 2015 18:33:54 +0000 (UTC) Received: by wibdy8 with SMTP id dy8so70572508wib.0 for ; Tue, 17 Mar 2015 11:33:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NSLpTy7HI10aEOp2qyX05PuWqXagha/ApNq5mftRUDE=; b=QbOvAf88RjfTOlM2G+gHck5UTSwtqZ/DEmHydagSlSMxYLVlWMX2skYiha00X50LaK eSAhHTvcQRyzSxgBNL7BC4IxX2ENC8/rQ6kpkDgu5o7xvg8ZMOLzgAyENUiJhc8L+KdJ w2PWCG8xVk53FJraN8Qm1nwogmDw+uFzYCbWy7crK98JenfqjwKVhiELONRe1AFjq3gC W3jsFXA+xbwkXxpe63QhGRFbt6LzeoElWnjT3dVthcN0rh4JM549Dh7lVkBGgwjTFobS q7BZ9Mogl0i8xfBYxKvc1zbw6xb8DAMRuKSJTR1rfRikPYqbPpM8AeywWOEFi1/Hi9yT ZuhQ== MIME-Version: 1.0 X-Received: by 10.180.106.197 with SMTP id gw5mr182727wib.58.1426617232580; Tue, 17 Mar 2015 11:33:52 -0700 (PDT) Received: by 10.27.52.75 with HTTP; Tue, 17 Mar 2015 11:33:52 -0700 (PDT) In-Reply-To: <5506A5BB.5060204@selasky.org> References: <5506A5BB.5060204@selasky.org> Date: Tue, 17 Mar 2015 11:33:52 -0700 Message-ID: Subject: Re: Unbalanced LACP link From: Jason Wolfe To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, Konstantin Kulikov , Vitalii Duk X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 18:33:54 -0000 On Mon, Mar 16, 2015 at 2:43 AM, Hans Petter Selasky wrote: > On 03/16/15 10:37, Vitalii Duk wrote: >> >> I've changed use_flowid to 0 and it helped! But isn't it setting >> significant? In a description it says "Shift flowid bits to prevent >> multiqueue collisions". > > > Hi, > > Maybe your ethernet hardware is not properly setting the m_flowid ... > > --HPS > Flip use_flowid back to 1 and try setting net.link.lagg.default_flowid_shift / net.link.lagg.X.flowid_shift to 0 as Hiren suggested. r260179 added this shift, which has caused us balancing issues with the i350/igb. https://svnweb.freebsd.org/base?view=revision&revision=260179 Based on Adrian's comment about igb/ixgbe not setting the 'full flowid' under normal conditions, does that mean this shift should be 0 by default to ensure we don't break balancing for devices that only set the CPU/MSIX queue? Jason