rdma_migrate_id(3) [centos man page]
RDMA_MIGRATE_ID(3) Librdmacm Programmer's Manual RDMA_MIGRATE_ID(3) NAME
rdma_migrate_id - Move a communication identifer to a different event channel. SYNOPSIS
#include <rdma/rdma_cma.h> int rdma_migrate_id (struct rdma_cm_id *id, struct rdma_event_channel *channel); ARGUMENTS
id An existing communication identifier to migrate. channel The communication channel that events associated with the allocated rdma_cm_id will be reported on. May be NULL. DESCRIPTION
Migrates a communication identifier to a different event channel. RETURN VALUE
Returns 0 on success, or -1 on error. If an error occurs, errno will be set to indicate the failure reason. NOTES
This routine migrates a communication identifier to the specified event channel and moves any pending events associated with the rdma_cm_id to the new channel. Users should not poll for events on the rdma_cm_id's current event channel or invoke other routines on the rdma_cm_id while migrating between channels. This call will block while there are any unacknowledged events on the current event channel. If the channel parameter is NULL, the specified rdma_cm_id will be placed into synchronous operation mode. All calls on the id will block until the operation completes. SEE ALSO
rdma_cm(7), rdma_create_event_channel(3), rdma_create_id(3), rdma_get_cm_event(3) librdmacm 2007-11-13 RDMA_MIGRATE_ID(3)
Check Out this Related Man Page
RDMA_CREATE_EVENT_CHANNEL(3) Librdmacm Programmer's Manual RDMA_CREATE_EVENT_CHANNEL(3) NAME
rdma_create_event_channel - Open a channel used to report communication events. SYNOPSIS
#include <rdma/rdma_cma.h> struct rdma_event_channel * rdma_create_event_channel (void); ARGUMENTS
void no arguments DESCRIPTION
Asynchronous events are reported to users through event channels. RETURN VALUE
Returns a pointer to the created event channel, or NULL if the request fails. On failure, errno will be set to indicate the failure rea- son. NOTES
Event channels are used to direct all events on an rdma_cm_id. For many clients, a single event channel may be sufficient, however, when managing a large number of connections or cm_id's, users may find it useful to direct events for different cm_id's to different channels for processing. All created event channels must be destroyed by calling rdma_destroy_event_channel. Users should call rdma_get_cm_event to retrieve events on an event channel. Each event channel is mapped to a file descriptor. The associated file descriptor can be used and manipulated like any other fd to change its behavior. Users may make the fd non-blocking, poll or select the fd, etc. SEE ALSO
rdma_cm(7), rdma_get_cm_event(3), rdma_destroy_event_channel(3) librdmacm 2007-05-15 RDMA_CREATE_EVENT_CHANNEL(3)