From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
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
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) [thread overview]
Message-ID: <20150531.214741.1556826335549377523.davem@davemloft.net> (raw)
In-Reply-To: <cover.1432927392.git.sowmini.varadhan@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@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.
prev parent reply other threads:[~2015-06-01 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 21:28 [PATCH 0/3] net/rds: SOL_RDS socket option to explicitly select transport Sowmini Varadhan
2015-05-29 21:28 ` [PATCH 1/3] net/rds: Declare SO_RDS_TRANSPORT and RDS_TRANS_* constants in uapi/linux/rds.h Sowmini Varadhan
2015-05-29 21:28 ` [PATCH 2/3] net/rds: Add setsockopt support for SO_RDS_TRANSPORT Sowmini Varadhan
2015-05-29 21:28 ` [PATCH 3/3] net/rds Add getsockopt " Sowmini Varadhan
2015-06-01 4:47 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150531.214741.1556826335549377523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=chien.yen@oracle.com \
--cc=igor.maximov@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sowmini.varadhan@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).