Searched refs:RDMA_MESSAGE_TENSOR_RE_REQUEST (Results 1 – 3 of 3) sorted by relevance
53 case RDMA_MESSAGE_TENSOR_RE_REQUEST: in MessageTypeToString()497 } else if (rm.type_ == RDMA_MESSAGE_TENSOR_RE_REQUEST) { in Process_CQ()1305 (rm.type_ == RDMA_MESSAGE_TENSOR_RE_REQUEST)) { in CreateMessage()1317 (rm.type_ == RDMA_MESSAGE_TENSOR_RE_REQUEST)) { in CreateMessage()1368 (rm.type_ == RDMA_MESSAGE_TENSOR_RE_REQUEST)) { in ParseMessage()1380 (rm.type_ == RDMA_MESSAGE_TENSOR_RE_REQUEST)) { in ParseMessage()1614 [this](const Status& s) { Send(RDMA_MESSAGE_TENSOR_RE_REQUEST); }); in RecvTensorMetaData()
51 * RDMA_MESSAGE_TENSOR_RE_REQUEST80 …equest. For traceability, the new message has a different name: **RDMA_MESSAGE_TENSOR_RE_REQUEST**.82 When the sender receives a **RDMA_MESSAGE_TENSOR_RE_REQUEST**, it will locate the relevant **RdmaTe…99 …_TENSOR_REQUEST**, **RDMA_MESSAGE_META_DATA_RESPONSE** and **RDMA_MESSAGE_TENSOR_RE_REQUEST**) is …156 * **RDMA_MESSAGE_TENSOR_RE_REQUEST** - (receiver ==> sender) Tensor re-request after meta-data upda…
81 RDMA_MESSAGE_TENSOR_RE_REQUEST, enumerator