|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | SYNOPSIS | ARGUMENTS | DESCRIPTION | RETURN VALUE | NOTES | INFINIBAND SPECIFIC | SEE ALSO | COLOPHON |
|
|
|
RDMA_RESOLVE_ADDR(3) Librdmacm Programmer's Manual RDMA_RESOLVE_ADDR(3)
rdma_resolve_addr - Resolve destination and optional source
addresses.
#include <rdma/rdma_cma.h>
int rdma_resolve_addr (struct rdma_cm_id *id, struct sockaddr
*src_addr, struct sockaddr *dst_addr, int timeout_ms);
id RDMA identifier.
src_addr Source address information. This parameter may be
NULL.
dst_addr Destination address information.
timeout_ms Time to wait for resolution to complete.
Resolve destination and optional source addresses from IP
addresses to an RDMA address. If successful, the specified
rdma_cm_id will be bound to a local device.
Returns 0 on success, or -1 on error. If an error occurs, errno
will be set to indicate the failure reason.
This call is used to map a given destination IP address to a
usable RDMA address. The IP to RDMA address mapping is done
using the local routing tables, or via ARP. If a source address
is given, the rdma_cm_id is bound to that address, the same as if
rdma_bind_addr were called. If no source address is given, and
the rdma_cm_id has not yet been bound to a device, then the
rdma_cm_id will be bound to a source address based on the local
routing tables. After this call, the rdma_cm_id will be bound to
an RDMA device. This call is typically made from the active side
of a connection before calling rdma_resolve_route and
rdma_connect.
This call maps the destination and, if given, source IP addresses
to GIDs. In order to perform the mapping, IPoIB must be running
on both the local and remote nodes.
rdma_create_id(3), rdma_resolve_route(3), rdma_connect(3),
rdma_create_qp(3), rdma_get_cm_event(3), rdma_bind_addr(3),
rdma_get_src_port(3), rdma_get_dst_port(3),
rdma_get_local_addr(3), rdma_get_peer_addr(3)
This page is part of the rdma-core (RDMA Core Userspace Libraries
and Daemons) project. Information about the project can be found
at ⟨https://github.com/linux-rdma/rdma-core⟩. If you have a bug
report for this manual page, send it to
[email protected]. This page was obtained from the
project's upstream Git repository
⟨https://github.com/linux-rdma/rdma-core.git⟩ on 2024-06-14. (At
that time, the date of the most recent commit that was found in
the repository was 2024-06-10.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
librdmacm 2007-10-31 RDMA_RESOLVE_ADDR(3)
Pages that refer to this page: rdma_bind_addr(3), rdma_create_id(3), rdma_create_qp(3), rdma_create_srq(3), rdma_get_cm_event(3), rdma_get_local_addr(3), rdma_get_peer_addr(3), rdma_get_src_port(3), rdma_join_multicast(3), rdma_join_multicast_ex(3), rdma_resolve_route(3), rdma_cm(7)
|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|