Date: Thu, 5 Jan 2017 20:18:24 -0700 From: Sean Bruno <sbruno@freebsd.org> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending Message-ID: <d6627189-c9ce-fc91-d71a-111e127b0b64@freebsd.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XJakuSKaqHqTnjkCXkf2062ux6Nr1763p Content-Type: multipart/mixed; boundary="tp6mSFJQkh8sAaD7HtXUsahMv6ilcehdm"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Message-ID: <d6627189-c9ce-fc91-d71a-111e127b0b64@freebsd.org> Subject: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending --tp6mSFJQkh8sAaD7HtXUsahMv6ilcehdm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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@ --tp6mSFJQkh8sAaD7HtXUsahMv6ilcehdm-- --XJakuSKaqHqTnjkCXkf2062ux6Nr1763p Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlhvDIBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmTZlggAwzQ4B/dxwOB5ID0jnpLPw5EiZ3lRUo0lu2QG8dBhGZLIGqWlRbJ/YQYE yPxmngf3c2n/y/eM1BRNFvuumy58VvcSRM2csFJAxMYHNHhIaz4u6IVhjj6Cn+Sl S+/SQMY3481iLIYWDwI7t9BTAlfXEBxIq65a8NW0JR1B9vT5UpohtTJb8Nvd1bRi AEZ7XHsNdhV6L2ichQCghUvF/ncIB9H3YZ8XlIpgjCHJtML9BRjB5ntBKAwLB4+/ KEW1AyhUtjLG8muHkYvqawn0EA948sf7q3hYDDCwW2tJKFX0WRGcOseZNi/mifah zAjf5HcBlqEMC6EPhoD5LxhOdH9n2w== =eg1J -----END PGP SIGNATURE----- --XJakuSKaqHqTnjkCXkf2062ux6Nr1763p--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6627189-c9ce-fc91-d71a-111e127b0b64>