From owner-freebsd-current@freebsd.org Tue Jan 10 03:31:45 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 87FE2CA8F5F for ; Tue, 10 Jan 2017 03:31:45 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A126109F for ; Tue, 10 Jan 2017 03:31:44 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id A307C1928BA for ; Tue, 10 Jan 2017 03:31:43 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: freebsd-current@freebsd.org References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> From: Sean Bruno Message-ID: Date: Mon, 9 Jan 2017 20:31:39 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vADxhef5KkwPUiR2pWscADVWhrT3uhDvH" 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: Tue, 10 Jan 2017 03:31:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vADxhef5KkwPUiR2pWscADVWhrT3uhDvH Content-Type: multipart/mixed; boundary="FqeFQjQK8UgO6w4uckhFVS1Eus2qrvToA"; protected-headers="v1" From: Sean Bruno To: freebsd-current@freebsd.org Message-ID: Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> In-Reply-To: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> --FqeFQjQK8UgO6w4uckhFVS1Eus2qrvToA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA violations this week. I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on IFLIB in the kernel. At this point, the driver deviates from Intel's code dramatically and you now get to yell directly into the freebsd-net@ megaphone for things that I may have broken. man page updates are coming up next. Please let us know if this revision has made things better, worse or none-of-the above on whatever Intel Gigabit NIC you happen to have lying around. sean On 01/05/17 20:17, Sean Bruno wrote: > tl;dr --> igbX devices will become emX devices >=20 > We're about to commit an update to sys/dev/e1000 that will implement an= d > activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all folk= s > who can test and poke at the drivers to do so this week. This will hav= e > 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. >=20 > 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. >=20 > 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. >=20 > UPDATING will be bumped to reflect these changes. >=20 > MFC to stable/11 will have a legacy implementation that doesn't use > IFLIB for compatibility reasons. >=20 > A documentation and man page update will follow in the next few days > explaining how to work with the changed driver. >=20 > sean >=20 > bcc net@ current@ re@ >=20 >=20 >=20 --FqeFQjQK8UgO6w4uckhFVS1Eus2qrvToA-- --vADxhef5KkwPUiR2pWscADVWhrT3uhDvH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh0VZtfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmRupAgAmibs1z/IH1o5M2ioRDG5lZAakfRu+QJYni9qPzfvEbJ0f3175RIPNiV7 /bGcCJ+GPg1UCKBjnZU6C+0/tdHysdJ0/YM+NRn6w/BmCWneJx4ZKgPWsZunoK0W wc3ntncrW75d6TXky0Fv+iXl2apifoaJEyT/vEdAHfjB/+L2ZsXPLekRsMLHz8lc A1XeJiq6CPnLxueMlB6MoO/Eh9oG3Omy6iD0oNOOTaGBeny4wcglJqEnWIpvbcTE jp5MbxY3G8YZ7XbqWZimu3UQpNkZSCglzsG/0ablipGZyroKid+vS11SD5EF+gpD xuusZK8h6GGGFcG67LFh5jBgxfws4g== =Sbup -----END PGP SIGNATURE----- --vADxhef5KkwPUiR2pWscADVWhrT3uhDvH--