> Subject: Re: [PATCH v5] bus/pci: netuio interface for windows > > Hi Tal, > > The issue I raised is slightly different: How do we distinguish between > different GUID_DEVCLASS_NET class devices - those that can support DPDK > and those that can't? > > For instance, say we have 3 NICs in the system - MLX5 NIC, Intel i40e NIC and > Intel ice NIC - all loaded with standard ethernet (NDIS) drivers. > > Now if I load and bind the netuio driver to the Intel ice NIC, I have one > GUID_DEVCLASS_NETUIO class device and two GUID_DEVCLASS_NET class > devices. > > If I run the pci scan now, it will detect all 3 devices and add them to the > list. > However, the Intel i40e NIC which is correctly detected as a > GUID_DEVCLASS_NET class and is bound to the standard NDIS driver cannot > support DPDK and should be excluded from the list. > > I think the suggestion at the community meeting was to define a DEV > interface which can be queried for confirming DPDK support. In such a case, > the MLX5 driver should support this interface, where as our standard i40e > (NDIS) driver will not. This check can be used to exclude this device from the > list. > > ranjit m.
Thanks for the explanation Ranjit, BTW, what will happen if a user does tries to use a NETUIO NIC recognized as NET? It will have nulls for the needed mem_resource fields so will it fails or crash?
