d6b92ffa99
kernel APIs. List of sources used: 1) rdma-core was cloned from "https://github.com/linux-rdma/rdma-core.git" Top commit d65138ef93af30b3ea249f3a84aa6a24ba7f8a75 2) OpenSM was cloned from git://git.openfabrics.org/~halr/opensm.git Top commit 85f841cf209f791c89a075048a907020e924528d 3) libibmad was cloned from "git://git.openfabrics.org/~iraweiny/libibmad.git" Tag 1.3.13 with some additional patches from Mellanox. 4) infiniband-diags was cloned from "git://git.openfabrics.org/~iraweiny/infiniband-diags.git" Tag 1.6.7 with some additional patches from Mellanox. Added the required Makefiles for building and installing. Sponsored by: Mellanox Technologies
53 lines
2.0 KiB
Groff
53 lines
2.0 KiB
Groff
.\" Licensed under the OpenIB.org BSD license (FreeBSD Variant) - See COPYING.md
|
|
.TH "RDMA_POST_SEND" 3 "2010-07-19" "librdmacm" "Librdmacm Programmer's Manual" librdmacm
|
|
.SH NAME
|
|
rdma_post_send \- post a work request to send a message.
|
|
.SH SYNOPSIS
|
|
.B "#include <rdma/rdma_verbs.h>"
|
|
.P
|
|
.B "int" rdma_post_send
|
|
.BI "(struct rdma_cm_id *" id ","
|
|
.BI "void *" context ","
|
|
.BI "void *" addr ","
|
|
.BI "size_t " length ","
|
|
.BI "struct ibv_mr *" mr ","
|
|
.BI "int " flags ");"
|
|
.SH ARGUMENTS
|
|
.IP "id" 12
|
|
A reference to a communication identifier where the message buffer
|
|
will be posted.
|
|
.IP "context" 12
|
|
User-defined context associated with the request.
|
|
.IP "addr" 12
|
|
The address of the memory buffer to post.
|
|
.IP "length" 12
|
|
The length of the memory buffer.
|
|
.IP "mr" 12
|
|
Optional registered memory region associated with the posted buffer.
|
|
.IP "flags" 12
|
|
Optional flags used to control the send operation.
|
|
.SH "DESCRIPTION"
|
|
Posts a work request to the send queue of the queue pair associated
|
|
with the rdma_cm_id. The contents of the posted buffer will be sent
|
|
to the remote peer of a connection.
|
|
.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"
|
|
The user is responsible for ensuring that the remote peer has queued a
|
|
receive request before issuing the send operations. For a list of
|
|
supported flags, see ibv_post_send. Unless the send request is using
|
|
inline data, the message buffer must have been registered
|
|
before being posted, with the mr parameter referencing the registration.
|
|
The buffer must remain registered until the send completes.
|
|
.P
|
|
Send operations may not be posted to an rdma_cm_id or the corresponding
|
|
queue pair until it has been connected.
|
|
.P
|
|
The user-defined context associated with the send request will be
|
|
returned to the user through the work completion wr_id, work request
|
|
identifier, field.
|
|
.SH "SEE ALSO"
|
|
rdma_cm(7), rdma_connect(3), rdma_accept(3),
|
|
ibv_post_send(3), rdma_post_sendv(3), rdma_post_recv(3)
|