This delta is very large, but its necessary. In preparation for full SRIOV support for this and the 40G
driver its necessary to seperate them.
We'll pop this into test and see what happens.
Do you want to update this comment to reflect 10/40gbe ethernet?
This requires a kernel options change in sys/conf ?
This also requires a kernel config change in GENERIC?
Same as earlier, should this be 10/40GBE?
Can you provide more details on why you need to separate them (and why you need to rename them)? Note that a single kld can contain multiple drivers (like if_lem.c and if_em.c in if_em.ko).
I do think having the kld name match the interface is good (so the ifconfig auto-load magic works), but it's not clear to me why you can't just include the VF driver in the PF driver's module? (And renaming options in a kernel config is pretty disruptive, so there need to be good reasons.. People are probably still somewhat burned over emX devices changing to igbX at one point.)
You mean to avoid having the driver claim the VFs? That is going to be solved differently I think. Ryan's SRIOV changes already allow the driver to be forced to be "ppt" to support pass through, and the devctl tool I'm committing in the next day or so will allow the administrator to change this on the fly. I think those are the better routes to address this.
@araujo I added inline comments to where I made the changes.
ixl is the one that is for 40GbE products; though that one's comment might need updating because there are X710/10gig products out there.
@araujo -- This is where you can change the media type to 10GbaseT, or other media types.
@araujo -- This is where 10GBaseT and other media types are added to the ifconfig -m list
What did you mean here Sean, this is not for 40G?
Oh, you may be right about GENERIC, I'll add that.
Are you confusing this with ixl/ixlv, or did you somehow want the 4x10 skew to