Increased paranoia of communication companies post NSA revelations
Hi all,
I work in the communications field and often have to carry out data gathering/analysis on customer's platforms for issue diagnosis.
In the last 2 months I have noticed a huge increase in distrust from African, Middle Eastern and Asian communication system operators of any data gathering/analysis of production data (even where everything remains on site).
I suspect that the NSA revelations of late may be having a knock on effect and was wondering if anyone else is finding customers tightening procedures around remote access of late?
Heyas
I'm currently trying to make a fresh build from scratch/source of FFMPEG.
This said, it brings quite a tail with it, so the use of a script was very obvious.
Anyway, i'm currently stuck at named package.
Lets ignore the tarball/download line, as the error is after.
Commands... (0 Replies)
RDMA_POST_RECV(3) Librdmacm Programmer's Manual RDMA_POST_RECV(3)NAME
rdma_post_recv - post a work request to receive an incoming message.
SYNOPSIS
#include <rdma/rdma_verbs.h>
int rdma_post_recv (struct rdma_cm_id *id, void *context, void *addr, size_t length, struct ibv_mr *mr);
ARGUMENTS
id A reference to a communication identifier where the message buffer will be posted.
context User-defined context associated with the request.
addr The address of the memory buffer to post.
length The length of the memory buffer.
mr A registered memory region associated with the posted buffer.
DESCRIPTION
Posts a work request to the receive queue of the queue pair associated with the rdma_cm_id. The posted buffer will be queued to receive an
incoming message sent by the remote peer.
RETURN VALUE
Returns 0 on success, or -1 on error. If an error occurs, errno will be set to indicate the failure reason.
NOTES
The user is responsible for ensuring that a receive buffer is posted and large enough to contain all sent data before the peer posts the
corresponding send message. The message buffer must have been registered before being posted, with the mr parameter referencing the regis-
tration. The buffer must remain registered until the receive completes.
Messages may be posted to an rdma_cm_id only after a queue pair has been associated with it. A queue pair is bound to an rdma_cm_id after
calling rdma_create_ep or rdma_create_qp, if the rdma_cm_id is allocated using rdma_create_id.
The user-defined context associated with the receive request will be returned to the user through the work completion wr_id, work request
identifier, field.
SEE ALSO rdma_cm(7), rdma_create_id(3), rdma_create_ep(3), rdma_create_qp(3), rdma_reg_read(3), ibv_reg_mr(3), ibv_dereg_mr(3), rdma_post_recvv(3),
rdma_post_send(3)librdmacm 2010-07-19 RDMA_POST_RECV(3)