From: Sowmini Varadhan <sowmini.varad...@oracle.com> Date: Fri, 29 May 2015 17:28:06 -0400
> Today the underlying transport (TCP or IB) for a PF_RDS socket is > implicitly selected based on the local address used to bind(2) the > PF_RDS socket. This results in some non-deterministic behavior when > there are un-numbered and IPoIB interfaces sharing the same IP address. > It also places the constraint that the IB interface must have an IP > address (and thus, IPoIB) configured on it. > > The non-determinism may be avoided by providing the user-space application > a socket option that allows it to explicitly select the transport > prior to bind(2). > > Patch 1 of this series provides the constant definitions needed by > the application via <linux/rds.h>. > > Patch 2 provides the setsockopt support, and Patch 3 provides the > getsockopt support. Seems reasonable, series applied to net-next, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
