> I disagree. A verbs consumer of mlx4 doesn't have to worry about the > internal design of the driver being different from mthca, and I would > hope that carries over to indentifying interrupts. It's much better for > users if we can just come up with a solution that handles both of your > cases at once, rather than an ad hoc solution for a subset of drivers.
I was not suggesting that we change the interface to verbs consumer/user or how we present the interrupt info. to user between mlx4 and mthca. I agree that it's much better if we can just come up with a solution that handles both. Any plan to merge the functionality of ib_core and mlx4_core into something like 'ofa_core' that will control resource allocation for both Infiniband and Ethernet functions? A single core will help in any similar resource issues. > I already suggested adding MSI-X vector information to > /sys/devices/... to match the existing "irq" file there. That would > allow userspace to figure out which interrupt belonged where. Jason's > idea of adding the PCI device name to the interrupt name seems viable to > me as well. > - R. Don't we need both /sys/devices/... and /proc/interrupts? Regards, Benjamin
_______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
