On 11/01/2018 03:18, Yuanhan Liu wrote: [..]
- Then inside the driver (say, i40e)* allocate 1 DPDK ethdev port * allocate 4 DPDK ethdev port, one for each VF specified by the vf_ports option. And these are VF representors. * link the VF representors to the right VF port For example, for i40e, it should be (from patch 3): vf = &pf->vfs[representor->vport_id]; * set the proper ethdev callbacks for the VF representors. As you can see, none of above complexity is introduced.
What springs to mind is whether this would end up delegating to the individual PMDs tasks that in the patchset are handled centrally in the library. Question is where the balance should be, and as an aside what should be the base-line requirements for a PMD to be "port representable".
..Remy
