From owner-freebsd-net@FreeBSD.ORG Tue Mar 17 19:34:32 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 489F56F8 for ; Tue, 17 Mar 2015 19:34:32 +0000 (UTC) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::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 09B40EC4 for ; Tue, 17 Mar 2015 19:34:32 +0000 (UTC) Received: by iegc3 with SMTP id c3so20394387ieg.3 for ; Tue, 17 Mar 2015 12:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UsTUjMJv5NaPAlcT+v9QP/A97KG2BAvRqbHVkEJEYiQ=; b=MP6r+N50VuCGOaHaxF8mkmjUUpF24/m0iMl7cFYpzK+u8YKW4Jb+E9D5LhBwAz5LtR TksaEoo6TW9Kzh9bwee9PmP/eRqf6tRYZXhT/4Q+MADhCmZIjyb690FH8KL8bD9aaYUD AoOqTkcxUiQgCuIJ84CFFsawOanKUpoy94W/Wblqc4uUzEI0sMDDIgpf5hdh44Dg5JoT U/JfKikkEhFqTZM7hpVmYk75vJH03qiBBtT+9dKSEwWH6D7y5z94/Afxq32xmE8PqxQ7 ErZsIqgzCg23ABOvp/CQ9IEk3PfAdYEiCaGHxk/PNsIlYnKxeNS5O+mfWJRhj6XmALUp VyLw== MIME-Version: 1.0 X-Received: by 10.50.143.42 with SMTP id sb10mr577329igb.49.1426620871333; Tue, 17 Mar 2015 12:34:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Tue, 17 Mar 2015 12:34:31 -0700 (PDT) In-Reply-To: References: <5506A5BB.5060204@selasky.org> Date: Tue, 17 Mar 2015 12:34:31 -0700 X-Google-Sender-Auth: 3Buda-AUw59gOZMxibhclaR7HAQ Message-ID: Subject: Re: Unbalanced LACP link From: Adrian Chadd To: Jason Wolfe Content-Type: text/plain; charset=UTF-8 Cc: Hans Petter Selasky , FreeBSD Net , 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 19:34:32 -0000 On 17 March 2015 at 11:33, Jason Wolfe wrote: > 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? Or we can just see if there's anything wrong with putting the full 32 bit RSS flowid in received packets that have them. -adrian