【RDMA】ibv_poll_cq()

目录

描述

参数

返回值

例子

常见问题

---

原文：https://www.rdmamojo.com/2013/02/15/ibv_poll_cq/  (强烈建议去看原文)

描述

ibv_poll_cq()从完成队列(CQ)轮询WC(工作完成)，非阻塞函数。

[工作完成] 表示 WQ(工作队列)中的WR(工作请求) 以及与CQ相关联的所有已发布到该工作队列的未发出信号的WR(工作请求)均已完成。

(A Work Completion indicates that a Work Request in a Work Queue, and all of the outstanding unsignaled Work Requests that posted to that Work Queue, associated with the CQ are done.)

任何发送和接收请求 以及以错误结束的发送请求，将在处理结束后生成WC(工作完成)。

(Any Receive Requests, signaled Send Requests and Send Requests that ended with an error will generate a Work Completion after their processing end.)

当[工作请求]结束时，会将[工作完成]添加到与此工作队列相关联的CQ的尾部。 ibv_poll_cq()检查CQ中是否存在[工作完成]，并按其输入顺序从CQ的顶部弹出(FIFO)。从CQ弹出[工作完成]后，无法将其返回给CQ。

应该以比产生WC更快的速度消费CQ中的WC，防止CQ队列溢出，如果发生CQ溢出，将触发异步事件IBV_EVENT_CQ_ERR，并且无法再使用CQ。

参数

Name	Direction	Description
cq	in	从ibv_create_cq()返回的CQ
num_entries	in	期望从CQ读取的WC数
wc	out	从CQ读取的WC数num_entries的数组。(Array of size num_entries of the Work Completions that will be read from the CQ)

结构ibv_wc描述了wc的属性。

struct ibv_wc {
    uint64_t        wr_id;
    enum ibv_wc_status    status;
    enum ibv_wc_opcode    opcode;
    uint32_t        vendor_err;
    uint32_t        byte_len;
    uint32_t        imm_data;
    uint32_t        qp_num;
    uint32_t        src_qp;
    int            wc_flags;
    uint16_t        pkey_index;
    uint16_t        slid;
    uint8_t            sl;
    uint8_t            dlid_path_bits;
};

这是struct ibv_wc的完整说明：

wr_id

与WR对应关联的64 bit值 (The 64 bits value that was associated with the corresponding Work Request)

status

Status of the operation. The value can be one of the following enumerated values and their numeric value: 操作状态。该值可以是下列枚举值及其数字值之一： IBV_WC_SUCCESS (0) - Operation completed successfully: this means that the corresponding Work Request (and all of the unsignaled Work Requests that were posted previous to it) ended and the memory buffers that this Work Request refers to are ready to be (re)used. IBV_WC_LOC_LEN_ERR (1) - Local Length Error: this happens if a Work Request that was posted in a local Send Queue contains a message that is greater than the maximum message size that is supported by the RDMA device port that should send the message or an Atomic operation which its size is different than 8 bytes was sent. This also may happen if a Work Request that was posted in a local Receive Queue isn't big enough for holding the incoming message or if the incoming me