Make iflib a loadable module.

[kib]

Summary

iflib is already a module, but it is unconditionally compiled into the kernel. There are drivers which do not need iflib(4), and there are situations where somebody might not want iflib in kernel because of using the corresponding driver as module.

[erj]

Would it be a good idea to group the iflib drivers together in the config files, so it's obvious there?

share/man/man4/ixgbe.4

42

lines

share/man/man4/vmx.4

28

lines

[kib]

Group drivers using iflib together for amd64, arm64, and i386 configs. line->liines.

[marius]

sys/dev/ixgbe/if_ixv.c appears to be missing a "MODULE_DEPEND(ixv, iflib, 1, 1, 1);" but while you are at it, you could remove its netmap dependency (now already provided by iflib.c) instead

sys/arm64/conf/GENERIC

148

• "PCEe" is probably a typo and was meant to read "PCIe" instead. However, at least em(4) also supports PCI-X and plain old PCI gear.
• The iflib grouping should probably include the vmx where already present.

Likewise for other GENERIC kernel config files.

[kib]

Handle Marius' comments.

[marius]

Well, I would just have went with "PCI" but if you prefer to state all variants :)

[erj]

In D19041#407181, @marius wrote:

Well, I would just have went with "PCI" but if you prefer to state all variants :)

You could also just drop "PCI", because iflib supposedly would support non-PCI ethernet devices. The devices that use it just happen to all present themselves on the PCI bus...

[marius]

Well, as-is iflib(4) in fact is PCI-specific.