On Mon, Oct 07, 2013 at 02:21:17PM -0400, Tejun Heo wrote: > Whee.... that's a lot more than I expected. I was just scanning > multiple msi users. Maybe we can stage the work in more manageable > steps so that you don't have to go through massive conversion only to > do it all over again afterwards and likewise people don't get > bombarded on each iteration? Maybe we can first update pci / msi code > proper, msi and then msix?
Multipe MSIs is just a handful of drivers, really. MSI-X impact still will be huge. But if we opt a different name for the new pci_enable_msix() then we could first update pci/msi, then drivers (in few stages possibly) and finally remove the old implementation. > tejun -- Regards, Alexander Gordeev [email protected] ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
