[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-28 Thread Thomas Monjalon
2014-05-23 00:10, Antti Kantee: > On 22/05/14 13:13, Thomas Monjalon wrote: > > 2014-05-19 16:51, Anatoly Burakov: > >> Note that since igb_uio no longer has a PCI ID list, it can now be > >> bound to any device, not just those explicitly supported by DPDK. In > >> other words, it now behaves simil

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-28 Thread Antti Kantee
On 28/05/14 13:45, Thomas Monjalon wrote: > So maybe it's possible to improve uio_pci_generic in order to replace igb_uio. > If someone wants to work on it, it's possible to stage uio_pci_generic in > dpdk.org in order to make it ready for kernel.org. Back when researching MSI + uio_pci_generic, I

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-28 Thread Stephen Hemminger
On Wed, 28 May 2014 15:45:02 +0200 Thomas Monjalon wrote: > 2014-05-23 00:10, Antti Kantee: > > On 22/05/14 13:13, Thomas Monjalon wrote: > > > 2014-05-19 16:51, Anatoly Burakov: > > >> Note that since igb_uio no longer has a PCI ID list, it can now be > > >> bound to any device, not just those e

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-27 Thread Xu, HuilongX
Note that since igb_uio no longer has a PCI ID list, it can now be bound to any device, not just those explicitly supported by DPDK. In other words, it now behaves similar to PCI stub, VFIO and other generic PCI drivers. Therefore to bind a new device to igb_uio, the user will now have to first wr

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-23 Thread Thomas Monjalon
2014-05-23 08:11, Stephen Hemminger: > On Thu, 22 May 2014 15:13:49 +0200 > > Thomas Monjalon wrote: > > 2014-05-19 16:51, Anatoly Burakov: > > > Note that since igb_uio no longer has a PCI ID list, it can now be > > > bound to any device, not just those explicitly supported by DPDK. In > > > oth

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-23 Thread Stephen Hemminger
On Thu, 22 May 2014 15:13:49 +0200 Thomas Monjalon wrote: > 2014-05-19 16:51, Anatoly Burakov: > > Note that since igb_uio no longer has a PCI ID list, it can now be > > bound to any device, not just those explicitly supported by DPDK. In > > other words, it now behaves similar to PCI stub, VFIO

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-23 Thread Antti Kantee
On 22/05/14 13:13, Thomas Monjalon wrote: > 2014-05-19 16:51, Anatoly Burakov: >> Note that since igb_uio no longer has a PCI ID list, it can now be >> bound to any device, not just those explicitly supported by DPDK. In >> other words, it now behaves similar to PCI stub, VFIO and other generic >>

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-22 Thread Thomas Monjalon
2014-05-22 13:24, Burakov, Anatoly: > Hi Thomas, > > > I wonder if we could replace igb_uio by uio_pci_generic? > > Can it do DMA or IOMMU support? Not even VFIO does everything we need, you > may have noticed that I have to go to PCI config space to enable bus > mastering. I don't think that dri

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-22 Thread Thomas Monjalon
2014-05-19 16:51, Anatoly Burakov: > Note that since igb_uio no longer has a PCI ID list, it can now be > bound to any device, not just those explicitly supported by DPDK. In > other words, it now behaves similar to PCI stub, VFIO and other generic > PCI drivers. I wonder if we could replace igb_u

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-22 Thread Burakov, Anatoly
Hi Thomas, > I wonder if we could replace igb_uio by uio_pci_generic? Can it do DMA or IOMMU support? Not even VFIO does everything we need, you may have noticed that I have to go to PCI config space to enable bus mastering. I don't think that driver can do either of those things. Unless, of co

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

2014-05-19 Thread Anatoly Burakov
Note that since igb_uio no longer has a PCI ID list, it can now be bound to any device, not just those explicitly supported by DPDK. In other words, it now behaves similar to PCI stub, VFIO and other generic PCI drivers. Therefore to bind a new device to igb_uio, the user will now have to first wr