File Manager

003 File Manager

Current Path: /usr/src/contrib/ofed/librdmacm/man

usr / src / contrib / ofed / librdmacm / man /

📁 ..
📄 CMakeLists.txt(1.2 KB)
📄 cmtime.1(1.53 KB)
📄 mckey.1(2.17 KB)
📄 rcopy.1(1.09 KB)
📄 rdma_accept.3(4.66 KB)
📄 rdma_ack_cm_event.3(821 B)
📄 rdma_bind_addr.3(1.29 KB)
📄 rdma_client.1(1.13 KB)
📄 rdma_cm.7(7.53 KB)
📄 rdma_connect.3(4.45 KB)
📄 rdma_create_ep.3(2.78 KB)
📄 rdma_create_event_channel.3(1.42 KB)
📄 rdma_create_id.3(2.36 KB)
📄 rdma_create_qp.3(2.02 KB)
📄 rdma_create_srq.3(1.85 KB)
📄 rdma_dereg_mr.3(1.15 KB)
📄 rdma_destroy_ep.3(629 B)
📄 rdma_destroy_event_channel.3(944 B)
📄 rdma_destroy_id.3(840 B)
📄 rdma_destroy_qp.3(595 B)
📄 rdma_destroy_srq.3(736 B)
📄 rdma_disconnect.3(972 B)
📄 rdma_event_str.3(625 B)
📄 rdma_free_devices.3(581 B)
📄 rdma_get_cm_event.3(8.17 KB)
📄 rdma_get_devices.3(983 B)
📄 rdma_get_dst_port.3(813 B)
📄 rdma_get_local_addr.3(854 B)
📄 rdma_get_peer_addr.3(797 B)
📄 rdma_get_recv_comp.3(1.39 KB)
📄 rdma_get_request.3(1.41 KB)
📄 rdma_get_send_comp.3(1.43 KB)
📄 rdma_get_src_port.3(803 B)
📄 rdma_getaddrinfo.3(4.63 KB)
📄 rdma_join_multicast.3(1.7 KB)
📄 rdma_leave_multicast.3(1.12 KB)
📄 rdma_listen.3(1.2 KB)
📄 rdma_migrate_id.3(1.49 KB)
📄 rdma_notify.3(1.72 KB)
📄 rdma_post_read.3(2 KB)
📄 rdma_post_readv.3(1.92 KB)
📄 rdma_post_recv.3(2.02 KB)
📄 rdma_post_recvv.3(1.96 KB)
📄 rdma_post_send.3(1.97 KB)
📄 rdma_post_sendv.3(1.87 KB)
📄 rdma_post_ud_send.3(2.07 KB)
📄 rdma_post_write.3(2.07 KB)
📄 rdma_post_writev.3(1.99 KB)
📄 rdma_reg_msgs.3(1.9 KB)
📄 rdma_reg_read.3(1.77 KB)
📄 rdma_reg_write.3(1.78 KB)
📄 rdma_reject.3(1.29 KB)
📄 rdma_resolve_addr.3(2.02 KB)
📄 rdma_resolve_route.3(1.1 KB)
📄 rdma_server.1(951 B)
📄 rdma_set_option.3(1.08 KB)
📄 rdma_xclient.1(1.37 KB)
📄 rdma_xserver.1(1.08 KB)
📄 riostream.1(2.17 KB)
📄 rping.1(1.7 KB)
📄 rsocket.7.in(6.18 KB)
📄 rstream.1(2.4 KB)
📄 ucmatose.1(2.47 KB)
📄 udaddy.1(2.11 KB)
📄 udpong.1(1.97 KB)

Editing: rdma_create_ep.3

.\" Licensed under the OpenIB.org BSD license (FreeBSD Variant) - See COPYING.md
.TH "RDMA_CREATE_EP" 3 "2010-07-19" "librdmacm" "Librdmacm Programmer's Manual" librdmacm
.SH NAME
rdma_create_ep \- Allocate a communication identifier and optional QP.
.SH SYNOPSIS
.B "#include <rdma/rdma_cma.h>"
.P
.B "int" rdma_create_ep
.BI "(struct rdma_cm_id **" id ","
.BI "struct rdma_addrinfo *" res ","
.BI "struct ibv_pd  *" pd ","
.BI "struct ibv_qp_init_attr *" qp_init_attr ");"
.SH ARGUMENTS
.IP "id" 12
A reference where the allocated communication identifier will be
returned.
.IP "res" 12
Address information associated with the rdma_cm_id returned from
rdma_getaddrinfo.
.IP "pd" 12
Optional protection domain if a QP is associated with the rdma_cm_id.
.IP "qp_init_attr" 12
Optional initial QP attributes.
.SH "DESCRIPTION"
Creates an identifier that is used to track communication information.
.SH "RETURN VALUE"
Returns 0 on success, or -1 on error.  If an error occurs, errno will be
set to indicate the failure reason.
.SH "NOTES"
After resolving address information using rdma_getaddrinfo, a user
may use this call to allocate an rdma_cm_id based on the results.
.P
If the rdma_cm_id will be used on the active side of a connection,
meaning that res->ai_flag does not have RAI_PASSIVE set, rdma_create_ep
will automatically create a QP on the rdma_cm_id if qp_init_attr is
not NULL.  The QP will be associated with the specified protection
domain, if provided, or a default protection domain if not.  Users
should see rdma_create_qp for details on the use of the pd and
qp_init_attr parameters.  After calling rdma_create_ep, the returned
rdma_cm_id may be connected by calling rdma_connect.  The active side
calls rdma_resolve_addr and rdma_resolve_route are not necessary.
.P
If the rdma_cm_id will be used on the passive side of a connection,
indicated by having res->ai_flag RAI_PASSIVE set, this call will save
the provided pd and qp_init_attr parameters.  When a new connection
request is retrieved by calling rdma_get_request, the rdma_cm_id
associated with the new connection will automatically be associated
with a QP using the pd and qp_init_attr parameters.  After calling
rdma_create_ep, the returned rdma_cm_id may be placed into a listening
state by immediately calling rdma_listen.  The passive side call
rdma_bind_addr is not necessary.  Connection requests may then be
retrieved by calling rdma_get_request.
.P
The newly created rdma_cm_id will be set to use synchronous operation.
Users that wish asynchronous operation must migrate the rdma_cm_id
to a user created event channel using rdma_migrate_id.
.P
Users must release the created rdma_cm_id by calling rdma_destroy_ep.
.SH "SEE ALSO"
rdma_cm(7), rdma_getaddrinfo(3), rdma_create_event_channel(3),
rdma_connect(3), rdma_listen(3), rdma_destroy_ep(3), rdma_migrate_id(3)

003 File Manager

Editing: rdma_create_ep.3

Upload File

Create Folder