[dpdk-dev] What to do about UIO breakage in 2.0

2015-04-28 Thread Stephen Hemminger
On Tue, 28 Apr 2015 08:07:18 + "Qiu, Michael" wrote: > On 4/28/2015 6:06 AM, Stephen Hemminger wrote: > > I raised the issue, but people seem to be ignoring that fact that igb_uio > > was broken by the introduction of UIO PCI generic in 2.0. > > What do you mean about igb_uio broken? > > Th

[dpdk-dev] What to do about UIO breakage in 2.0

2015-04-28 Thread Qiu, Michael
On 4/28/2015 6:06 AM, Stephen Hemminger wrote: > I raised the issue, but people seem to be ignoring that fact that igb_uio > was broken by the introduction of UIO PCI generic in 2.0. What do you mean about igb_uio broken? Thanks, Michael > > There are three options: > 1. Remove IGB_UIO only use

[dpdk-dev] What to do about UIO breakage in 2.0

2015-04-27 Thread Matthew Hall
Stephen, This mail is a bit confusing for end users of DPDK which might be why you didn't get many replies yet. If I understand this mail right, you're saying that nothing works? Or it works, but igb_uio doesn't work, and the performance isn't good because MSI-X is not working? I am confused w

[dpdk-dev] What to do about UIO breakage in 2.0

2015-04-27 Thread Stephen Hemminger
I raised the issue, but people seem to be ignoring that fact that igb_uio was broken by the introduction of UIO PCI generic in 2.0. There are three options: 1. Remove IGB_UIO only use UIO PCI generic. Downside there is no MSI-X support for UIO PCI generic. 2. Revert UIO PCI generic support