From owner-freebsd-net@freebsd.org Mon Aug 8 13:52:20 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8ABBBB1237 for ; Mon, 8 Aug 2016 13:52:20 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 38CE4199A for ; Mon, 8 Aug 2016 13:52:20 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id x83so15557970wma.3 for ; Mon, 08 Aug 2016 06:52:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=ALcW34bTAlDaYN57FYIzOLHPsGxe1f4Li2jreOmvMCI=; b=D6VC0gJXASa4AOqt7WgUYRk3f7DSnBS3pPprtBfi6ptGcPPY84YEVwCU9dArqgjbpC zMQZObw/9t7QZNcsC4DTz1uNvOd7BAfZWjNXllGPVtfq11lDhTd3zvUO6CcdDjfcQjLI SmUqR1U4U54yI8KmUcry7KJmUQWMClKkXj1eb0BGrIR0X0yM8xMVO59Z9ftDojYCZ8Vs lPKrinOLTFIOXWIE9T9w+b5GYqXW9DLymaloTX2xD1CFmQexKDexHjdgqYs1uAkc/kqS pXrs2h5pvpZvZvW39qB5q2xTCtPtVX9pMRHstAtHKYz18Fi0Cvun7jOF2aNczNAqgWN/ +Skw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=ALcW34bTAlDaYN57FYIzOLHPsGxe1f4Li2jreOmvMCI=; b=dwceTT6VrLpxowZhoN5HCyoEzX2bbNtHF9pRSQy942PoBn1iViZ7+34RrqDAHY+b6W 9o7+tp/0BJyqcB5l3ArC+ToWOqQG9mAkntZ76Jif0BYh0fwsUnYmKSgz78a/I2rCjTei j9Ugpp5p9nEa0ZziKW5IZIsVO0/OKsQrtFTCOhObCHnmpqdJTr6uqV8cBxecYYo3IOoM ouliCOOdrVpoeiMiRhVjpeDAp5E9kbzFHuzNQRPFBspnGzZ3/7I403K4sF9gyqgP9Zwx USo0HsGOWh8+X0cxTnLX2ntJSFLgii5RbfqKeaK0UPKZzsDmjtzXwrkYlBi49dS+UvK1 wH9A== X-Gm-Message-State: AEkoousc5AgCrJx56ks8CqsVBA7tApu6fEbTwHx3V+wg4f9Jvcb/Ck/VA9Vfe2+YZ5bZpA== X-Received: by 10.194.238.42 with SMTP id vh10mr83212288wjc.111.1470664337998; Mon, 08 Aug 2016 06:52:17 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (LFbn-1-7077-85.w90-116.abo.wanadoo.fr. [90.116.246.85]) by smtp.gmail.com with ESMTPSA id a2sm33055708wjg.46.2016.08.08.06.52.17 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Aug 2016 06:52:17 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Unstable local network throughput From: Ben RUBSON In-Reply-To: Date: Mon, 8 Aug 2016 15:52:16 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <647B1F5C-EF03-4DC5-B5AC-75AD1995A20B@gmail.com> References: <3C0D892F-2BE8-4650-B9FC-93C8EE0443E1@gmail.com> <3B164B7B-CBFB-4518-B57D-A96EABB71647@gmail.com> <5D6DF8EA-D9AA-4617-8561-2D7E22A738C3@gmail.com> <06E414D5-9CDA-46D1-A26F-0B07E76FDB34@gmail.com> <0b14bf39-ed71-b9fb-1998-bd9676466df6@selasky.org> To: freebsd-net X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2016 13:52:20 -0000 > On 05 Aug 2016, at 10:30, Hans Petter Selasky wrote: >=20 > On 08/04/16 23:49, Ben RUBSON wrote: >>>=20 >>> On 04 Aug 2016, at 20:15, Ryan Stone wrote: >>>=20 >>> On Thu, Aug 4, 2016 at 11:33 AM, Ben RUBSON = wrote: >>> But even without RSS, I should be able to go up to 2x40Gbps, don't = you think so ? >>> Nobody already did this ? >>>=20 >>> Try this patch >>> (...) >>=20 >> I also just tested the NODEBUG kernel but it did not help. >=20 > Hi, >=20 > When running these tests, do you see any CPUs fully utilised? No, CPUs look like this on both servers : 27 processes: 1 running, 26 sleeping CPU 0: 1.1% user, 0.0% nice, 16.7% system, 0.0% interrupt, 82.2% = idle CPU 1: 1.1% user, 0.0% nice, 18.9% system, 0.0% interrupt, 80.0% = idle CPU 2: 1.9% user, 0.0% nice, 17.8% system, 0.0% interrupt, 80.4% = idle CPU 3: 1.1% user, 0.0% nice, 15.2% system, 0.0% interrupt, 83.7% = idle CPU 4: 0.4% user, 0.0% nice, 16.3% system, 0.0% interrupt, 83.3% = idle CPU 5: 1.1% user, 0.0% nice, 14.4% system, 0.0% interrupt, 84.4% = idle CPU 6: 2.6% user, 0.0% nice, 17.4% system, 0.0% interrupt, 80.0% = idle CPU 7: 2.2% user, 0.0% nice, 15.2% system, 0.0% interrupt, 82.6% = idle CPU 8: 1.1% user, 0.0% nice, 3.0% system, 15.9% interrupt, 80.0% = idle CPU 9: 0.0% user, 0.0% nice, 3.0% system, 32.2% interrupt, 64.8% = idle CPU 10: 0.0% user, 0.0% nice, 0.4% system, 58.9% interrupt, 40.7% = idle CPU 11: 0.0% user, 0.0% nice, 0.4% system, 77.4% interrupt, 22.2% = idle CPU 12: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 13: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 14: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 15: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 16: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 17: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 18: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 19: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 20: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 21: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% = idle CPU 22: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle CPU 23: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle Load is correctly spread over the NUMA connected to the NIC (the first = 12 CPUs). There is clearly enough power to fulfill the full-duplex link ! I tried many cpuset configurations (IRQs over the 12 CPUs etc...), but = no improvement at all. > Did you check the RX/TX pauseframes settings and the mlx4 sysctl = statistics counters, if there is packet loss? I tried to disable RX/TX pauseframes, but it did not help. And "sysctl -a | grep mlx | grep err" counters are all 0. I also played with ring size, adaptive interrupt moderation... with no = luck. Ben