Lines Matching +full:side +full:- +full:by +full:- +full:side

11 possibility to either write data from an sg list to the remote side
12 or to request ("read") data transfer from the remote side into a given
15 RTRS provides I/O fail-over and load-balancing capabilities by using
17 Documentation/ABI/testing/sysfs-class-rtrs-client).
19 RTRS is used by the RNBD (RDMA Network Block Device) modules.
26 --------
29 server side for a given client for rdma transfer. A session
36 chunks reserved for him on the server side. Their number, size and addresses
49 discussed in LPC RDMA MC 2019. When always_invalidate=Y, on the server side we
64 ------------------------
67 by one via attaching RTRS_MSG_CON_REQ messages to the rdma_connect requests.
69 established. They are used by the server to find a persisting session/path or
77 2. Server accepts the connection requests one by one and attaches
79 protocol version, the messages include error code, queue depth supported by
93 (i.e. steps 1-4 finished for all paths requested for a session)
97 side or network outage in an absence of IO.
105 RTRS_MSG_CON_REQ  ------------------->
106                    <------------------- RTRS_MSG_CON_RSP
109 RTRS_MSG_INFO_REQ ------------------->
110                    <------------------- RTRS_MSG_INFO_RSP
112                    -------------------> [RTRS_HB_MSG_IMM]
113 [RTRS_HB_MSG_ACK] <-------------------
114 [RTRS_HB_MSG_IMM] <-------------------
115                    -------------------> [RTRS_HB_MSG_ACK]
118 -------
123 on the server side and rdma writes there the user data, user header and the
126 been accessed and at what offset the RTRS_MSG_RDMA_WRITE can be found by
134 usr_data + usr_hdr + rtrs_msg_rdma_write -----------------> [RTRS_IO_REQ_IMM]
135 [RTRS_IO_RSP_IMM]                        <----------------- (id + errno)
140 on the server side and rdma writes there the user data, user header and the
143 been accessed and at what offset the RTRS_MSG_RDMA_WRITE can be found by
155 usr_data + usr_hdr + rtrs_msg_rdma_write -----------------> [RTRS_IO_REQ_IMM]
156 [RTRS_MSG_RKEY_RSP]                     <----------------- (RTRS_MSG_RKEY_RSP)
157 [RTRS_IO_RSP_IMM]                        <----------------- (id + errno)
163 on the server side and rdma writes there the user header and the
174 usr_hdr + rtrs_msg_rdma_read --------------> [RTRS_IO_REQ_IMM]
175 [RTRS_IO_RSP_IMM]            <-------------- usr_data + (id + errno)
177 [RTRS_IO_RSP_IMM_W_INV]      <-------------- usr_data + (INV) + (id + errno)
182 on the server side and rdma writes there the user header and the
198 usr_hdr + rtrs_msg_rdma_read --------------> [RTRS_IO_REQ_IMM]
199 [RTRS_IO_RSP_IMM]            <-------------- usr_data + (id + errno)
200 [RTRS_MSG_RKEY_RSP]	     <----------------- (RTRS_MSG_RKEY_RSP)
202 [RTRS_IO_RSP_IMM_W_INV]      <-------------- usr_data + (INV) + (id + errno)