From owner-freebsd-current@freebsd.org Wed Jan 18 07:34:13 2017 Return-Path: Delivered-To: freebsd-current@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 B5560CB5444 for ; Wed, 18 Jan 2017 07:34:13 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C8E31BCB; Wed, 18 Jan 2017 07:34:12 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LdHeL-1cu39J43FJ-00iUXg; Wed, 18 Jan 2017 08:34:05 +0100 Date: Wed, 18 Jan 2017 08:34:04 +0100 From: "O. Hartmann" To: Sean Bruno Cc: freebsd-current Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending Message-ID: <20170118083400.11156f23@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ptGLgElCy3e29G9ccPPmopNhOdvtBdCDt3DEg5+eJVeyrSbY8my NEyMm9h9baBxnUsPK2d+vymDtYKt99ODOCYPhLBZtUzc1rzRVT9Riz9/Q6j9PcjkjUYEo61 pB4ZvxNz7wfrWqxPdI3IAqTAK9fPmQwSxZ2u/HCwqpAzwtqObe1MvaceiSrelG12ZkdAzHx MVCikHc3Bl7+O25yqt1OQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:R6/ZgTNfq+U=:mZG6tZNyklobIqf+qGZtgy 7rRw0I7xg7xL7/J079sheVTlig1p9oPQ7K18vvPPBa4pWrhV4TGem/wGMhFOXlt6MqUDdUheP v5bkchZ8hxMt1lKw/MxsFc5FG8n0eXNsHcgssitIKV7eBpBPb7/HCL3H/ztxcmZCx7D2Yw//c pXPq59MyzAjldaa2zkNkb2mxKqnwivyWxNqd/dcPQirk9JELUtILCQOGvTdK1O1E1rYW99sc7 +IzgcmMsy6ef112fCGRW1afTCBekHIqCvPABfEJuXPBVZaRUDohTWQIHYGziU517oqCuI0s/K YWTPgBjuyVpJ+LwgyDILs6OUZMG7R+ljMGU7GSS48h54cWUZ8jagjH4ybH14R+zqry0IAXgnk jr/x5H9YHQQhzkW5lBXvm/PMzKayN1xPKBrQN3oD12DDKuq+nwpM8zkIk7xZRfINvmN1sFVHw DYdiE1xWks2GQfI0hYuZLIPqUxFKOoX1lIYkX7u5YoG2v4c0Szaft8jI8AnyB5FM5hcy7Snmb SJ3Nvo/dV3S+6kPcIyBPID21+JXnxieu6KSyAN8ouJViJBQT3qiGeRbqWg2XFnLMqN+Onkp/X Ob9BkH+vTQKBsE2YUOvIkYgDMc25tRcxDKbRV3ysVCfLweCIEM6lm4eZdXGnMWaXLNOA4Wjtj mLalDa5KyQlnCSoLXS7ftVH4xSbX1xYcbscCSwServz93a+C7t6p6yIydANHe8F2rU6Wl1/n2 qC/hWilDPn6HqK4ayNiGIpKn230HskiOGa+PV0l0jb4KIMey3hwxTXRILOC1qCo3VfnCYU+DZ tav1vmR X-Mailman-Approved-At: Wed, 18 Jan 2017 11:58:56 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 07:34:13 -0000 On Thu, 5 Jan 2017 20:17:56 -0700 Sean Bruno wrote: > tl;dr --> igbX devices will become emX devices > > We're about to commit an update to sys/dev/e1000 that will implement and > activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all folks > who can test and poke at the drivers to do so this week. This will have > some really great changes for performance and standardization that have > been bouncing around inside of various FreeBSD shops that have been > collaborating with Matt Macy over the last year. > > This will implement multiple queues for certain em(4) devices that are > capable of such things and add some new sysctl's for you to poke at in > your monitoring tools. > > Due to limitations of device registration, igbX devices will become emX > devices. So, you'll need to make a minor update to your rc.conf and > scripts that manipulate the network devices. > > UPDATING will be bumped to reflect these changes. > > MFC to stable/11 will have a legacy implementation that doesn't use > IFLIB for compatibility reasons. > > A documentation and man page update will follow in the next few days > explaining how to work with the changed driver. > > sean > > bcc net@ current@ re@ > > > On a Fujitsu Celsius M740, the "em0" device gets stuck on heavy I/O. I can still trigger this behaviour on recent CURRENT (12.0-CURRENT #17 r312369: Wed Jan 18 06:18:45 CET 2017 amd64) by rsync'ing a large poudriere ports repository onto a remote NFSv4 fileserver. The freeze always occur on large tarballs. Again, here is the pciconf output of the device: em0@pci0:0:25:0: class=0x020000 card=0x11ed1734 chip=0x153a8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection I217-LM' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfb300000, size 131072, enabled bar [14] = type Memory, range 32, base 0xfb339000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0xf020, size 32, enabled On another box. equipted with a dual-port Intel i350 NIC, the igb0 and igb1 do have negotiation problems with several types of switches (in my SoHo environment, I use a Netgear GS110TP, at work there are several types of Cisco Catalyst 3XXX types). The igbX very often fall back to 100MBit/s. Since yesterday, the igbX on that specific i350 basesd NIC (we have plentz of them and they show similar phenomena with FreeBSD), although the switch reports an uplink with 1 GBit, FreeBSD CURRENT shows this weird crap message: > igb0: flags=8843 metric 0 mtu > 1500 > options=653dbb > ether xx:xx:xx:xx:xx:xx inet 192.168.0.111 netmask 0xffffff00 broadcast > 192.168.0.255 nd6 options=29 > media: Ethernet autoselect (100baseTX ) > status: active I haven't checked whether FreeBSD lies or the switch lies about the linkspeed, but will do next time I have access to the box. regards, Oliver