Lines Matching full:communication
201 * rdma_create_event_channel - Open a channel used to report communication events.
215 * rdma_destroy_event_channel - Close an event communication channel.
216 * @channel: The communication channel to destroy.
229 * rdma_create_id - Allocate a communication identifier.
230 * @channel: The communication channel that events associated with the
232 * @id: A reference where the allocated communication identifier will be
237 * Creates an identifier that is used to track communication information.
240 * communication. The difference is that RDMA communication requires
241 * explicitly binding to a specified RDMA device before communication
242 * can occur, and most operations are asynchronous in nature. Communication
254 * rdma_create_ep - Allocate a communication identifier and qp.
255 * @id: A reference where the allocated communication identifier will be
263 * Create an identifier and option QP used for communication.
280 * rdma_destroy_ep - Deallocates a communication identifier and qp.
281 * @id: The communication identifier to destroy.
291 * rdma_destroy_id - Release a communication identifier.
292 * @id: The communication identifier to destroy.
496 * communication events. In most cases, use of this routine is not
521 * @id: Communication identifier associated with the request.
542 * @id: Communication identifier associated with the request.
558 * rdma_get_cm_event - Retrieves the next pending communication event.
560 * @event: Allocated information about the next communication event.
562 * Retrieves a communication event. If no events are pending, by default,
577 * rdma_ack_cm_event - Free a communication event.
652 * @id: Communication identifier to set option for.
663 * @id: Communication identifier to migrate.