[dpdk-dev] [PATCH v9 02/14] eal_pci: Add flag to hold kernel driver type

2015-02-20 Thread Tetsuya Mukawa
On 2015/02/19 22:29, Tetsuya Mukawa wrote: > On 2015/02/19 20:17, Thomas Monjalon wrote: >>> @@ -152,6 +159,7 @@ struct rte_pci_device { >>> uint16_t max_vfs; /**< sriov enable if not zero */ >>> int numa_node; /**< NUMA node connection */ >>>

[dpdk-dev] [PATCH v9 02/14] eal_pci: Add flag to hold kernel driver type

2015-02-19 Thread Tetsuya Mukawa
On 2015/02/19 20:17, Thomas Monjalon wrote: >> @@ -152,6 +159,7 @@ struct rte_pci_device { >> uint16_t max_vfs; /**< sriov enable if not zero */ >> int numa_node; /**< NUMA node connection */ >> struct rte_devargs *devargs;

[dpdk-dev] [PATCH v9 02/14] eal_pci: Add flag to hold kernel driver type

2015-02-19 Thread Thomas Monjalon
> @@ -152,6 +159,7 @@ struct rte_pci_device { > uint16_t max_vfs; /**< sriov enable if not zero */ > int numa_node; /**< NUMA node connection */ > struct rte_devargs *devargs;/**< Device user arguments */ > + enum

[dpdk-dev] [PATCH v9 02/14] eal_pci: Add flag to hold kernel driver type

2015-02-19 Thread Tetsuya Mukawa
From: Michael Qiu Currently, dpdk has no ability to know which type of driver( vfio-pci/igb_uio/uio_pci_generic) the device used. It only can check whether vfio is enabled or not staticly. It really useful to have the flag, becasue different type need to handle