To mimic sockets, rdma_set_service_type() is perfectly correct and usable by socket offloaders such as SDP and RDS, so they can translate an IP_TOS setsockopt() call to rdma_set_service_type(). This plugs to the case where the application wants to request per connection QoS class.
Adding the SID to the PR query is easy enough to do. Here's the issue that I would like to resolve first.
Starting first with something transport neutral, I propose the using rdma_set_service_type() combined with the flowinfo in the IPv6 address. If we can agree that this is usable, now let's add the SID to the PR query.
Since, SID -> QoS, and rdma_set_service_type() sets the QoS, what gets set in the PR query? The SID -> QoS may not match the QoS requested by the application. Should the SID always be set, or only if QoS is not specified through some other means?
- Sean _______________________________________________ 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
