Unify all Intel gigabit drivers into a single iflib implementation.
Details
Details
- Reviewers
franco_opnsense.org sbruno - Group Reviewers
Intel Networking - Commits
- rS311849: Migrate e1000 to the IFLIB framework:
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 6533 Build 6758: arc lint + arc unit
Event Timeline
Comment Actions
I have not done anything more than *compile* tested this.
It is missing legacy mode and should not be committed as-is.
Comment Actions
Make a if_igb.ko (legacy) and an if_igb_iflib.ko so that we have
the ability to test this stuff out before going live.
Comment Actions
I need to actually test this somewhere, but it compiles a legacy and iflib module now.
Comment Actions
Updating to capture all the things.
This unifies lem, em and igb into one 'em' device, enables multiple
queues in em(4) when supported.
Comment Actions
Purge legacy driver support from 12-current version. We'll do the
legacy/iflib dance for the MFC to 11-stable.
Comment Actions
Due to POLA issues, Matt is using the suggestions from John to create
an igbX device to keep users from being SUPER angry when this lands
later today.
Comment Actions
Changes need to be made to build and use if_lem for the boards that need it. Also, we are going to install a symlink from if_em.ko to if_igb.ko such that users of modules don't get immediately hosed on an update if they aren't building the drivers into the kernel and are expecting loader.conf 'if_igb_load=YES' to work.
Comment Actions
Address review comments:
- restore broken white space
- remove uneeded #ifdef KLD_MODULE
Add installation of symlink during installkernel so that loader.conf:if_igb_load=YES
still works for users who are currently using igb(4) as a module and don't have em(4)
loaded or built into their kernel.