Lines Matching full:rdma

48  * RDMA identifier and release all resources allocated with the device.
84  * RDMA CM.
235  * @ps: RDMA port space.
239  *   Rdma_cm_id's are conceptually equivalent to a socket for RDMA
240  *   communication.  The difference is that RDMA communication requires
241  *   explicitly binding to a specified RDMA device before communication
305  * rdma_bind_addr - Bind an RDMA identifier to a source address.
306  * @id: RDMA identifier.
311  *   will also be bound to a local RDMA device.
324  * @id: RDMA identifier.
330  *   to an RDMA address.  If successful, the specified rdma_cm_id will
333  *   This call is used to map a given destination IP address to a usable RDMA
339  *   an RDMA device.  This call is typically made from the active side of a
350  * @id: RDMA identifier.
353  *   Resolves an RDMA route to the destination address in order to establish
366  * @id: RDMA identifier.
373  *   The rdma_cm_id must be bound to a local RDMA device before calling this
380  *   domain associated with the underlying RDMA device.
392  * @id: RDMA identifier.
405  * @id: RDMA identifier.
423  * @id: RDMA identifier.
433  *   address and the associated RDMA device.  If the rdma_cm_id is bound
434  *   to an RDMA port number only, the listen will occur across all RDMA
458  *   socket, but the rdma_cm_id is bound to a specific RDMA device.
477  *   to reject the request.  If the underlying RDMA transport supports
488  * @id: RDMA identifier.
510  * @id: RDMA identifier.
528  *   an RDMA device by calling rdma_bind_addr or rdma_resolve_addr.  Use of
530  *   multicast address to an RDMA device.  The user must call
602  * rdma_get_devices - Get list of RDMA devices currently available.
605  *   Return a NULL-terminated array of opened RDMA devices.  Callers can use
606  *   this routine to allocate resources on specific RDMA devices that will be
627  * rdma_event_str - Returns a string representation of an rdma cm event.
669  * rdma_getaddrinfo - RDMA address and route resolution service.