Lines Matching full:communication
301 * ib_cm_handler - User-defined callback to process communication events.
302 * @cm_id: Communication identifier associated with the reported event.
303 * @event: Information about the communication event.
305 * IB_CM_REQ_RECEIVED and IB_CM_SIDR_REQ_RECEIVED communication events
310 * to a user's existing communication identifier.
313 * however, returning a non-zero value instructs the communication manager to
333 * ib_create_cm_id - Allocate a communication identifier.
334 * @device: Device associated with the cm_id. All related communication will
337 * @context: User specified context associated with the communication
340 * Communication identifiers are used to track connection states, service
483 * communication events. Events that should be reported to the CM and
548 * @cm_id: Communication identifier associated with the QP attributes to
596 * @cm_id: Communication identifier that will be associated with the
616 * @cm_id: Communication identifier associated with the received service ID