1RDMA_CREATE_EP(3) Librdmacm Programmer's Manual RDMA_CREATE_EP(3)
2
3
4
6 rdma_create_ep - Allocate a communication identifier and optional QP.
7
9 #include <rdma/rdma_cma.h>
10
11 int rdma_create_ep (struct rdma_cm_id **id, struct rdma_addrinfo *res,
12 struct ibv_pd *pd, struct ibv_qp_init_attr *qp_init_attr);
13
15 id A reference where the allocated communication identifier
16 will be returned.
17
18 res Address information associated with the rdma_cm_id returned
19 from rdma_getaddrinfo.
20
21 pd Optional protection domain if a QP is associated with the
22 rdma_cm_id.
23
24 qp_init_attr
25 Optional initial QP attributes.
26
28 Creates an identifier that is used to track communication information.
29
31 Returns 0 on success, or -1 on error. If an error occurs, errno will
32 be set to indicate the failure reason.
33
35 After resolving address information using rdma_getaddrinfo, a user may
36 use this call to allocate an rdma_cm_id based on the results.
37
38 If the rdma_cm_id will be used on the active side of a connection,
39 meaning that res->ai_flag does not have RAI_PASSIVE set, rdma_create_ep
40 will automatically create a QP on the rdma_cm_id if qp_init_attr is not
41 NULL. The QP will be associated with the specified protection domain,
42 if provided, or a default protection domain if not. Users should see
43 rdma_create_qp for details on the use of the pd and qp_init_attr param‐
44 eters. After calling rdma_create_ep, the returned rdma_cm_id may be
45 connected by calling rdma_connect. The active side calls
46 rdma_resolve_addr and rdma_resolve_route are not necessary.
47
48 If the rdma_cm_id will be used on the passive side of a connection,
49 indicated by having res->ai_flag RAI_PASSIVE set, this call will save
50 the provided pd and qp_init_attr parameters. When a new connection
51 request is retrieved by calling rdma_get_request, the rdma_cm_id asso‐
52 ciated with the new connection will automatically be associated with a
53 QP using the pd and qp_init_attr parameters. After calling rdma_cre‐
54 ate_ep, the returned rdma_cm_id may be placed into a listening state by
55 immediately calling rdma_listen. The passive side call rdma_bind_addr
56 is not necessary. Connection requests may then be retrieved by calling
57 rdma_get_request.
58
59 The newly created rdma_cm_id will be set to use synchronous operation.
60 Users that wish asynchronous operation must migrate the rdma_cm_id to a
61 user created event channel using rdma_migrate_id.
62
63 Users must release the created rdma_cm_id by calling rdma_destroy_ep.
64
66 rdma_cm(7), rdma_getaddrinfo(3), rdma_create_event_channel(3),
67 rdma_connect(3), rdma_listen(3), rdma_destroy_ep(3), rdma_migrate_id(3)
68
69
70
71librdmacm 2010-07-19 RDMA_CREATE_EP(3)