From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 0/3] net/rds: SOL_RDS socket option to explicitly select transport Date: Sun, 31 May 2015 21:47:41 -0700 (PDT) Message-ID: <20150531.214741.1556826335549377523.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, chien.yen@oracle.com, rds-devel@oss.oracle.com, ajaykumar.hotchandani@oracle.com, igor.maximov@oracle.com To: sowmini.varadhan@oracle.com Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Sowmini Varadhan 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 . > > Patch 2 provides the setsockopt support, and Patch 3 provides the > getsockopt support. Seems reasonable, series applied to net-next, thanks.