remove same process transport shortcutting mechanism in rpc

Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

BUG: 1223 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1223

1 files changed, 0 insertions, 24 deletions

diff --git a/rpc/rpc-lib/src/rpc-transport.h b/rpc/rpc-lib/src/rpc-transport.h
index 5698b287cce..69a768d7283 100644
--- a/rpc/rpc-lib/src/rpc-transport.h
+++ b/rpc/rpc-lib/src/rpc-transport.h
@@ -181,29 +181,8 @@ struct rpc_transport {
         void                      *notify_data;
 	peer_info_t                peerinfo;
 	peer_info_t                myinfo;
-
-        rpc_transport_t           *peer_trans;
-        struct {
-                pthread_mutex_t       mutex;
-                pthread_cond_t        cond;
-                pthread_t             thread;
-                struct list_head      msgs;
-                /* any request/reply will be transformed as pollin data on the
-                 * peer, hence we are building up a pollin data even before
-                 * handing it over to peer rpc_transport. In order to decide whether
-                 * the pollin data is vectored or simple, we follow a simple
-                 * algo i.e., if there is a progpayload in request/reply, its
-                 * considered vectored, otherwise its a simple pollin data.
-                 */
-                rpc_transport_pollin_t   *msg;
-        } handover;
 };
 
-typedef struct {
-        rpc_transport_pollin_t *pollin;
-        struct list_head    list;
-} rpc_transport_handover_t;
-
 struct rpc_transport_ops {
         /* no need of receive op, msg will be delivered through an event
          * notification
@@ -261,9 +240,6 @@ int32_t
 rpc_transport_unref (rpc_transport_t *trans);
 
 int
-rpc_transport_setpeer (rpc_transport_t *trans, rpc_transport_t *trans_peer);
-
-int
 rpc_transport_register_notify (rpc_transport_t *trans, rpc_transport_notify_t,
                                void *mydata);