On Wed, Feb 3, 2016 at 12:39 PM, Kamil Rytarowski <krytarowski at caviumnetworks.com> wrote: > W dniu 03.02.2016 o 09:47, David Marchand pisze: >> And do your custom things in its devinit function ? > > I'm requesting from PF the mode of the device to be initialized. This part > is handled dynamically and depends of the current configuration in PF. > > In my use-case there are two device types: primary (master) and secondary > (slave). For the primary VF I'm creating a DPDK port normally, for secondary > I retain configured PCI device for further reuse (and there is no port > created).
Well, again, if you don't want to associate a port to this pci resource, why are you registering a eth_driver ? A eth_driver driver supposes you have a 1 - 1 relation between ethdev and pci resource. For your case, register a pci driver, then in your pci probing function (.devinit), depending on what you want to do, you can either do nothing (?) or create one or more ethdevs (see mlx* and cxgbe drivers). -- David Marchand