【vbers】ibv_poll_cq()|RDMA_work request flushed error-程序员宅基地

技术标签: RDMA  

目录

描述

参数

返回值

例子

常见问题


原文: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 message size if greater the maximum message size supported by the RDMA device port that received the message.
  • IBV_WC_LOC_QP_OP_ERR (2) - Local QP Operation Error: an internal QP consistency error was detected while processing this Work Request: this happens if a Work Request that was posted in a local Send Queue of a UD QP contains an Address Handle that is associated with a Protection Domain to a QP which is associated with a different Protection Domain or an opcode which isn't supported by the transport type of the QP isn't supported (for example: RDMA Write over a UD QP).
  • IBV_WC_LOC_EEC_OP_ERR (3) - Local EE Context Operation Error: an internal EE Context consistency error was detected while processing this Work Request (unused, since its relevant only to RD QPs or EE Context, which aren’t supported).
  • IBV_WC_LOC_PROT_ERR (4) - Local Protection Error: the locally posted Work Request’s buffers in the scatter/gather list does not reference a Memory Region that is valid for the requested operation.
  • IBV_WC_WR_FLUSH_ERR (5) - Work Request Flushed Error: A Work Request was in process or outstanding when the QP transitioned into the Error State.
  • IBV_WC_MW_BIND_ERR (6) - Memory Window Binding Error: A failure happened when tried to bind a MW to a MR.
  • IBV_WC_BAD_RESP_ERR (7) - Bad Response Error: an unexpected transport layer opcode was returned by the responder. Relevant for RC QPs.
  • IBV_WC_LOC_ACCESS_ERR (8) - Local Access Error: a protection error occurred on a local data buffer during the processing of a RDMA Write with Immediate operation sent from the remote node. Relevant for RC QPs.
  • IBV_WC_REM_INV_REQ_ERR (9) - Remote Invalid Request Error: The responder detected an invalid message on the channel. Possible causes include the operation is not supported by this receive queue (qp_access_flags in remote QP wasn't configured to support this operation), insufficient buffering to receive a new RDMA or Atomic Operation request, or the length specified in a RDMA request is greater than 2^{31} bytes. Relevant for RC QPs.
  • IBV_WC_REM_ACCESS_ERR (10) - Remote Access Error: a protection error occurred on a remote data buffer to be read by an RDMA Read, written by an RDMA Write or accessed by an atomic operation. This error is reported only on RDMA operations or atomic operations. Relevant for RC QPs.
  • IBV_WC_REM_OP_ERR (11) - Remote Operation Error: the operation could not be completed successfully by the responder. Possible causes include a responder QP related error that prevented the responder from completing the request or a malformed WQE on the Receive Queue. Relevant for RC QPs.
  • IBV_WC_RETRY_EXC_ERR (12) - Transport Retry Counter Exceeded: The local transport timeout retry counter was exceeded while trying to send this message. This means that the remote side didn't send any Ack or Nack. If this happens when sending the first message, usually this mean that the connection attributes are wrong or the remote side isn't in a state that it can respond to messages. If this happens after sending the first message, usually it means that the remote QP isn't available anymore. Relevant for RC QPs.
  • IBV_WC_RNR_RETRY_EXC_ERR (13) - RNR Retry Counter Exceeded: The RNR NAK retry count was exceeded. This usually means that the remote side didn't post any WR to its Receive Queue. Relevant for RC QPs.
  • IBV_WC_LOC_RDD_VIOL_ERR (14) - Local RDD Violation Error: The RDD associated with the QP does not match the RDD associated with the EE Context (unused, since its relevant only to RD QPs or EE Context, which aren't supported).
  • IBV_WC_REM_INV_RD_REQ_ERR (15) - Remote Invalid RD Request: The responder detected an invalid incoming RD message. Causes include a Q_Key or RDD violation (unused, since its relevant only to RD QPs or EE Context, which aren't supported)
  • IBV_WC_REM_ABORT_ERR (16) - Remote Aborted Error: For UD or UC QPs associated with a SRQ, the responder aborted the operation.
  • IBV_WC_INV_EECN_ERR (17) - Invalid EE Context Number: An invalid EE Context number was detected (unused, since its relevant only to RD QPs or EE Context, which aren't supported).
  • IBV_WC_INV_EEC_STATE_ERR (18) - Invalid EE Context State Error: Operation is not legal for the specified EE Context state (unused, since its relevant only to RD QPs or EE Context, which aren't supported).
  • IBV_WC_FATAL_ERR (19) - Fatal Error.
  • IBV_WC_RESP_TIMEOUT_ERR (20) - Response Timeout Error.
  • IBV_WC_GENERAL_ERR (21) - General Error: other error which isn't one of the above errors.
opcode The operation that the corresponding Work Request performed. This value controls the way that data was sent, the direction of the data flow and the valid attributes in the Work Completion. The value can be one of the following enumerated values:

相应的工作请求执行的操作。此值控制数据的发送方式、数据流的方向以及“工作完成”中的有效属性。该值可以是下列枚举值之一:

  • IBV_WC_SEND - 已发布到“发送队列”中的WR的发送操作(Send operation for a WR that was posted to the Send Queue) 
  • IBV_WC_RDMA_WRITE - 已发布到发送队列的WR的RDMA写操作(RDMA Write operation for a WR that was posted to the Send Queue)
  • IBV_WC_RDMA_READ - 已发布到发送队列的WR的RDMA读取操作(RDMA Read operation for a WR that was posted to the Send Queue)
  • IBV_WC_COMP_SWAP - 已发布到“发送队列”中的WR的比较和交换操作(Compare and Swap operation for a WR that was posted to the Send Queue)
  • IBV_WC_FETCH_ADD - 已发布到发送队列的WR的获取和添加操作(Fetch and Add operation for a WR that was posted to the Send Queue)
  • IBV_WC_BIND_MW - 已发布到“发送队列”中的WR的“内存窗口”绑定操作(Memory Window bind operation for a WR that was posted to the Send Queue)
  • IBV_WC_RECV - 发送已发布到(QP或SRQ的)接收队列的WR的数据操作(Send data operation for a WR that was posted to a Receive Queue (of a QP or to an SRQ))
  • IBV_WC_RECV_RDMA_WITH_IMM -  发送到(QP或SRQ)的接收队列的WR的带立即数的RDMA。对于此操作码,仅消耗一个接收请求,并且未使用此RR的sg_list(RDMA with immediate for a WR that was posted to a Receive Queue (of a QP or to an SRQ). For this opcode, only a Receive Request was consumed and the sg_list of this RR wasn't used)
vendor_err

供应商特定的错误,如果completion 因错误而结束,则会提供更多信息。一旦WC以错误结束,该值向RDMA设备的供应商提供有关失败原因的提示。

byte_len

传输的字节数。与incoming Send或 RDMA Write with immediate operations的接收队列有关。该值不包括立即数的长度(如果存在)。与RDMA读取和原子操作的“发送队列”相关。对于不与SRQ关联的UD QP的接收队列,或者对于与UD QP关联的SRQ,该值等于消息的有效负载加上为GRH保留的40个字节。传输的字节数是消息的有效负载加上为GRH保留的40个字节(无论是否存在GRH)

(The number of bytes transferred. Relevant if the Receive Queue for incoming Send or RDMA Write with immediate operations. This value doesn't include the length of the immediate data, if such exists. Relevant in the Send Queue for RDMA Read and Atomic operations.For the Receive Queue of a UD QP that is not associated with an SRQ or for an SRQ that is associated with a UD QP this value equals to the payload of the message plus the 40 bytes reserved for the GRH.The number of bytes transferred is the payload of the message plus the 40 bytes reserved for the GRH, whether or not the GRH is present)

imm_data

(可选)以网络顺序的SEND或RDMA WRITE操作码中的32 bit 数字,与有效载荷一起发送到远程端,并放置在[接收工作完]( Receive Work Completion)成中,而不是在远端内存缓冲区中。如果设置了IBV_WC_WITH_IMM,则此值有效

qp_num

已完成的WR的本地QP的号码。与和SRQ相关的[接收工作完成](Receive Work Completions)相关.

(Local QP number of completed WR. Relevant for Receive Work Completions that are associated with an SRQ)

src_qp Source QP number (remote QP number) of completed WR. Relevant for Receive Work Completions of a UD QP
wc_flags Flags of the Work Completion. It is either 0 or the bitwise OR of one or more of the following flags:

  • IBV_WC_GRH - Indicator that GRH is present for a Receive Work Completions of a UD QP. If this bit is set, the first 40 bytes of the buffered that were referred to in the Receive request will contain the GRH of the incoming message. If this bit is cleared, the content of those first 40 bytes is undefined
  • IBV_WC_WITH_IMM - Indicator that imm_data is valid. Relevant for Receive Work Completions
pkey_index P_Key index. Relevant for GSI QPs
slid Source LID (the base LID that this message was sent from). Relevant for Receive Work Completions of a UD QP
sl Service Level (the SL LID that this message was sent with). Relevant for Receive Work Completions of a UD QP
dlid_path_bits Destination LID path bits. Relevant for Receive Work Completions of a UD QP (not applicable for multicast messages)

以下测试(opcode & IBV_WC_RECV)将指示 来自接收队列的完成状态。(The following test (opcode & IBV_WC_RECV) will indicate that the status of a completion is from the Receive Queue.)
对于UD QP的[接收工作完成](receive Work Completions),无论是否设置了IBV_WC_GRH位,数据均从已发布的接收缓冲区的偏移量40开始。
并非所有wc属性始终有效。如果完成状态不是IBV_WC_SUCCESS,则仅以下属性有效:

  • wr_id
  • status
  • qp_num
  • vendor_err

返回值

Value Description
正数

从CQ读取的WC数及其值在wc中返回。如果该值小于num_entries,则表示CQ中没有更多的工作完成。如果此值等于num_entries,则CQ中可能会有更多的工作完成

0 CQ为空
负数

尝试从CQ读取WC(工作完成)时发生故障

例子

从CQ轮询WC(工作完成)(在轮询模式下):

struct ibv_wc wc;

int num_comp;

 
do {
    num_comp = ibv_poll_cq(cq, 1, &wc);
} while (num_comp == 0);
 
if (num_comp < 0) {
    fprintf(stderr, "ibv_poll_cq() failed\n");
    return -1;
}
 
/* verify the completion status */
if (wc.status != IBV_WC_SUCCESS) {
    fprintf(stderr, "Failed status %s (%d) for wr_id %d\n", 
        ibv_wc_status_str(wc.status),
        wc.status, (int)wc.wr_id);
    return -1;
}

常见问题

那工作完成(WC)到底是什么?

工作完成意味着相应的工作请求已结束,缓冲区可以(重新)用于读取,写入或释放。

ibv_poll_cq()是否引起上下文切换?

否。Work Completions的轮询根本不会导致上下文切换;它不会导致上下文切换。这就是为什么RDMA技术可以实现极低的延迟(低于1 usc)的原因。

Is there a limit to the number of Work Completions that can we polled when calling ibv_poll_cq()?

调用ibv_poll_cq()时可以轮询的[工作完成](Work Completions 数量是否有限制?

没有,你想读多少都行。

我调用了ibv_poll_cq(),它填充了我提供给它的所有数组。我能否知道CQ中还有多少工作完成?

不,你不能。

我从UD QP的接收队列中获得了工作完成(WC),并且进展顺利。我从内存缓冲区中读取了数据,但数据不正确。为什么?

也许您查看了数据的起始偏移量0。对于UD QP的任何工作完成,无论是否存在GRH,数据都将放置在相关内存缓冲区的偏移量40中。


什么是GRH,为什么我需要它?
全局路由头(GRH)提供的信息对于将消息发回给此消息的发件人(如果来自其他子网或来自多播组)最有用。

I've got completion with error status. Can I read all of the Work Completion fields?


否。如果“工作完成”状态表明存在错误,则仅以下属性有效:wr_id,status,qp_num和vendor_err。其余属性未定义。

我从CQ上Read了一个WC,但我不需要,我可以将其退还给CQ吗?

不,你不能。

我可以阅读属于特定工作队列的工作完成吗?(Can I read Work Completion that belongs to a specific Work Queue?

不,你不能。


如果添加的工作完成(WC)数量超过CQ的size,将会发生什么情况?


CQ将超限,并且CQ(以及与之关联的所有QP)将进入错误状态。

版权声明:本文为博主原创文章,遵循 CC 4.0 BY-SA 版权协议,转载请附上原文出处链接和本声明。
本文链接:https://blog.csdn.net/bandaoyu/article/details/116493052

智能推荐

(精确度,召回率,真阳性,假阳性)ACC、敏感性、特异性等 ROC指标_真阳性率-程序员宅基地

文章浏览阅读2.5w次,点赞14次,收藏109次。(精确度,召回率,真阳性,假阳性)ACC、敏感性、特异性等 ROC指标,计算原理,依次列出。_真阳性率

Java垃圾回收机制

Java垃圾回收机制

如何判断第三方软件测试公司是否具有资质

通过查看公司资质证书、考察公司规模和团队实力、查看历史案例和客户评价、询问测试流程和方法、考虑保密性和安全性以及比较多个公司的报价和服务,您可以做出明智的选择,为软件项目的成功奠定坚实的基础。一个有资质的软件测试公司通常会拥有相关的行业认证,如CMA/CNAS等,这些认证证明了公司在质量管理、项目管理等方面的实力和能力。了解公司的测试团队,包括团队成员的背景、经验和技术水平。了解公司的规模,包括员工数量、办公环境等,这有助于判断公司的实力和稳定性。比较多个公司的报价和服务,选择性价比高的公司。

音箱一通电就嗡嗡响已修好_多媒体音箱常见故障和解决办法?学习下-程序员宅基地

文章浏览阅读3.5w次。对于大部分的用户来说,在多媒体音箱的使用上都不会有特别的讲究,很多用户由于对产品结构的陌生以及相关知识的缺乏,往往在音箱出现小故障之后也是凑合着用,实在不行再重新换过,事实上多媒体音箱的不少故障修理都非常简单,一般的用户都可以轻松搞定。一、调整音量时出现噼里啪啦的声音,音量时大时小。这是在多媒体音箱身上出现次数最多的故障,相信很多用户都有这样的体会,在使用一段时间后,调节音箱的音量往往会出现这个情..._音箱一通电就嗡嗡响怎么办

深度学习9-使用强化学习进行股票交易_强化学习做股票-程序员宅基地

文章浏览阅读1.8k次。强化学习_强化学习做股票

浅谈数据中心网络结构的发展历程-程序员宅基地

文章浏览阅读689次。传统数据中心的网络架构数据中心计算网络主要由大量的二层接入设备与少量的三层设备组成的网络结构,是传统上标准的三层结构:1、接入层,用于连接所有的计算节点,在目前的数据中心中,通常以机柜交换机的形式存在;2、汇聚层,用于接入层的互联,并作为该汇聚区域二三层的边界,同时各种防火墙、负载均衡等业务也部署于此;3、核心层,用于汇聚层的的互联,并实现整个数..._数据中心网络结构的发展历史

随便推点

PADS VX 2.7与WIN 10更配哦_pads win10适合安装哪个版本pads-程序员宅基地

文章浏览阅读4.8k次。在WIN 10下之前装的PADS VX2.3,_pads win10适合安装哪个版本pads

unzip实现一次性解压多个文件夹,并且直接覆盖_win7 unzip 多个文件-程序员宅基地

文章浏览阅读7.4k次。最近在实现文件上传的时候,经常需要同一个文件夹上传多个相同路径的情况,就觉着这样很耗时间,特别是网速慢的时候,一个一个去上传,那是非常的慢,于是网上搜寻了一下一次性解压多个文件夹的命令之类的。都不太如意,于是就自己写了一个sh脚本。#!/bin/bash#本sh主要用于unzip解压多个文件夹的命令#事先获取需要解压的文件路径个数echo "正在检索文件夹:$#"#获取压缩的zip文件_win7 unzip 多个文件

Science新闻:肠道菌群又添一大功能,揭示你的真实年龄_深度学习+肠道菌群+免疫组学-程序员宅基地

文章浏览阅读4.8k次。文章目录肠道菌群又添一大功能,揭示你的真实年龄写在前面热心肠日报摘要背景研究方法数据获取神经网络训练回归分类过采样特征重要性研究结果机器学习预测年龄微生物对年龄预测的影响结论Science新闻介绍Reference译者简介猜你喜欢写在后面肠道菌群又添一大功能,揭示你的真实年龄撰文:陈亮 中科院微生物所责编:刘永鑫写在前面日前从热心肠日报看到,Science杂志发了一则新闻:肠道里的细菌可..._深度学习+肠道菌群+免疫组学

大一python编程题库和答案,大一python题库及答案_有一个列表['python','programmer','internet','crawler'],-程序员宅基地

文章浏览阅读1k次,点赞20次,收藏16次。大家好,给大家分享一下大一python基础编程题答案,很多人还不知道这一点。下面详细解释一下。现在让我们来看看!_有一个列表['python','programmer','internet','crawler'],编写程序统计该列

SAP物料标准成本估算结果_sap 委外物料标准成本核算-程序员宅基地

文章浏览阅读7.3k次,点赞6次,收藏7次。SAP物料标准成本估算(CK11N/CK40N)的结果保存在相关表格:KEKO,CKIS (CKIP,CKIT) ._sap 委外物料标准成本核算

sql拼接同一字段中的数据_用SQL将Oracle中同一列的多行记录拼接成一个字符串-程序员宅基地

文章浏览阅读442次。-- 原始数据-- a 111-- b 222-- a 333-- a 444-- b 555-- 最终结果-- a 111*333*444SELECTL4.L_TIME,MAX(SUBSTR(L4.分组内容,2)) 最终字段值FROM(SELECTL3.L_TIME,SYS_CONNECT_BY_PATH(L3.L_CONTENT,'*') AS 分组内容FROM(SEL..._sql同一列的做个值进行拼接