src/sys/dev/ixgbe, branch release/8.1.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F8.1.0 2010-05-24T18:00:28Z MFC of driver version 2.2.0 for 8.1 2010-05-24T18:00:28Z Jack F Vogel jfv@FreeBSD.org 2010-05-24T18:00:28Z urn:sha1:2a147bb27e89398f3cdc6a42f72c1ca6822660a2 MFC of version 2.1.7 of the ixgbe driver. 2010-04-05T18:46:29Z Jack F Vogel jfv@FreeBSD.org 2010-04-05T18:46:29Z urn:sha1:d4e2e2a53f013f49b53afe5785c9eba0cab99712 MFC r203834 and r205197: Make ALTQ work for drbr consumers. 2010-03-18T17:00:44Z Max Laier mlaier@FreeBSD.org 2010-03-18T17:00:44Z urn:sha1:29f2c008fd146c26e0bfe5c5f9d11e26ec44974b MFC a number of changes from head for ISP (203478,203463,203444,202418,201758, 2010-02-11T18:34:06Z Matt Jacob mjacob@FreeBSD.org 2010-02-11T18:34:06Z urn:sha1:7733cf8fffadd4b286f7ed03e7748ee70e36433d 201408,201325,200089,198822,197373,197372,197214,196162). Since one of those changes was a semicolon cleanup from somebody else, this touches a lot more. This patch seperates the control of header split from LRO (which it 2009-09-04T22:37:03Z Jack F Vogel jfv@FreeBSD.org 2009-09-04T22:37:03Z urn:sha1:0bb40ca3e0009f29079191f1910386c5cda2ddd7 was previously dependent on), LRO gets turned off when bridging but its been found that header split is still a performance win in that case. Secondly, there was some interface specific control in stats code that has been missing, and a logic error that resulted in bogus reporting. Thanks to Manish and John of LineRateSystems for the report and help in this code. Approved by: re Improvement on the last change, this gives a precise 2009-07-24T21:35:52Z Jack F Vogel jfv@FreeBSD.org 2009-07-24T21:35:52Z urn:sha1:45289e2ded0ec138bd46b0016ada1008d1bc4a0c way to tell the one and only interface that a vlan event is for. Thanks to John Baldwin for the patch. Approved by: re This delta fixes two bugs: 2009-07-24T16:57:49Z Jack F Vogel jfv@FreeBSD.org 2009-07-24T16:57:49Z urn:sha1:387424df40d26125deb66790003549747d706da7 - When a vlan event occurs a check was not made that the event was actually for the interface, thus resulting in a panic. All three drivers have this vulnerability. Add a check for this condition. - Secondly, there was a duplicate buf_ring free in the em driver resulting in a panic on unload. Remove. Approved by: re Multiqueue RX is not correctly enabled on the new 82599 2009-07-01T16:13:01Z Jack F Vogel jfv@FreeBSD.org 2009-07-01T16:13:01Z urn:sha1:6bdcc991ae9d0973edfcd08a1d8de6b61d500d54 adapter, the SRRCTL register needs to be setup per queue. Approved by: re Use if_maddr_rlock()/if_maddr_runlock() rather than IF_ADDR_LOCK()/ 2009-06-26T11:45:06Z Robert Watson rwatson@FreeBSD.org 2009-06-26T11:45:06Z urn:sha1:eb956cd041f956275522092d6ba66671356ff84f IF_ADDR_UNLOCK() across network device drivers when accessing the per-interface multicast address list, if_multiaddrs. This will allow us to change the locking strategy without affecting our driver programming interface or binary interface. For two wireless drivers, remove unnecessary locking, since they don't actually access the multicast address list. Approved by: re (kib) MFC after: 6 weeks Decided to limit the interrupt bind to multiqueue 2009-06-25T18:40:27Z Jack F Vogel jfv@FreeBSD.org 2009-06-25T18:40:27Z urn:sha1:29af53f0063adcbeb8a8890a57eb2c4f00c2d178 config as done in igb.