From: Sean Hefty <sean.hefty@intel.com>
Date: Mon, 4 Jun 2012 20:22:10 +0000 (-0700)
Subject: rsocket: Handle TCP_MAXSEG socket option
X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=3593589a3e9bfc8bbaab75b45e090182313a69dc;p=~shefty%2Flibrdmacm.git

rsocket: Handle TCP_MAXSEG socket option

netperf uses the TCP_MAXSEG socket option.  Add support for it.
Problem reported by Sridhar Samudrala <sri@us.ibm.com>

Signed-off-by: Sean Hefty <sean.hefty@intel.com>
---

diff --git a/src/rsocket.c b/src/rsocket.c
index a1679f16..e899e8ae 100644
--- a/src/rsocket.c
+++ b/src/rsocket.c
@@ -1717,6 +1717,9 @@ int rsetsockopt(int socket, int level, int optname,
 			opt_on = *(int *) optval;
 			ret = 0;
 			break;
+		case TCP_MAXSEG:
+			ret = 0;
+			break;
 		default:
 			break;
 		}
@@ -1814,6 +1817,12 @@ int rgetsockopt(int socket, int level, int optname,
 			*((int *) optval) = !!(rs->tcp_opts & (1 << optname));
 			*optlen = sizeof(int);
 			break;
+		case TCP_MAXSEG:
+			*((int *) optval) = (rs->cm_id && rs->cm_id->route.num_paths) ?
+					    1 << (7 + rs->cm_id->route.path_rec->mtu) :
+					    2048;
+			*optlen = sizeof(int);
+			break;
 		default:
 			ret = ENOTSUP;
 			break;