Content-Type: multipart/mixed; boundary="===============2908755987486808746==" MIME-Version: 1.0 From: sekar.srinivasan at wdc.com Subject: [SPDK] SPDK initiator does not seem to honor Responder Resource value exchanged during RDMA connection establishment Date: Wed, 03 Nov 2021 18:51:49 +0000 Message-ID: <20211103185149.2830.64848@ml01.vlan13.01.org> List-ID: To: spdk@lists.01.org --===============2908755987486808746== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Issue Summary: SPDK initiator does not seem to honor Responder Resource val= ue exchanged during RDMA connection establishment Details: During the MAD Connect sequence for establishing an RDMA IO connection for = RoCEv2 (NVMe-over Fabrics), the SPDK initiator provides the following value= s in the REQ message: =E2=80=A2 Initiator Depth: 0 =E2=80=A2 Responder Resources: 16 The target sends a Connect Reply with the following parameters in the REP m= essage: =E2=80=A2 Initiator Depth: 16 =E2=80=A2 Responder Resources: 16 This should result in the target being able to have 16 outstanding RDMA Rea= d Requests at any time on that IO connection. Based on Ethernet trace analy= sis, it is observed that the SPDK initiator sends a NAK (Invalid Request) o= n reception of the 9th RDMA Read Request. If the target is modified to igno= re the parameters exchanged in the MAD sequence and hard code the Responder= Resources to 8, no issues are observed. What could be causing the SPDK ini= tiator to expect the value of 8 for Responder Resources? --===============2908755987486808746==--