>What about for IB HCAs? Are there a large number >of options that have not yet been exposed but >which are device independent and *might* be >desirable to control? If not, then why introduce >a "catchall" interface as opposed to specific >interfaces that have to justified on a per >method basis?
Sockets provides setsockopt/getsockopt calls, and there is an attempt here to emulate sockets. These calls provide a very simple way to extend functionality without needing to modify the user to kernel transition code with every feature. Functionality that I would like to add through these calls in the short term include: * Bind to a device based on IB specific addresses (e.g. GIDs). * Getting usable path records between two nodes. * Setting primary and alternate paths for a connection. * Modify an alternate path for a connection. * Joining a multicast group identified by an IP address. * Leaving a multicast group identified by an IP address. * Joining a multicast group identified by an MCMemberRecord. * Leaving a multicast group identified by an MCMemberRecord. - Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
