From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============4468332901066869662=="
MIME-Version: 1.0
From: Valeriy Glushkov <valeriy.glushkov at starwind.com>
Subject: Re: [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target
Date: Thu, 07 Feb 2019 15:37:30 +0000
Message-ID: <op.zwuloox2ns8zkg@sam8>
In-Reply-To: 0500ca29-968c-7003-d0b5-66698f890606@dev.mellanox.co.il
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============4468332901066869662==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi Sasha,

There is no IBV on the host side, it's Windows.
So we have no control over the RNR field.

 From a RDMA session's dump I can see that the initiator sets  =

infiniband.cm.req.rnrretrcount to 0x6.

Could the RNR value be related to the problem we have with SPDK 19.01  =

NVMeoF target?

-- =

Best regards,
Valeriy Glushkov
www.starwind.com
valeriy.glushkov(a)starwind.com

Sasha Kotchubievsky <sashakot(a)dev.mellanox.co.il> =D0=BF=D0=B8=D1=81=D0=
=B0=D0=BB(=D0=B0) =D0=B2 =D1=81=D0=B2=D0=BE=D1=91=D0=BC =D0=BF=D0=B8=D1=81=
=D1=8C=D0=BC=D0=B5  =

Thu, 07 Feb 2019 16:31:33 +0200:

> Hi,
>
> What "rnr count" value you set in initiator side at connect to NVMF? Do  =

> you see**any *IBV_WC_RNR_RETRY_EXC_ERR *error in initiator side?
>
> Best regards
>
> Sasha
>
>
> On 2/7/2019 6:50 AM, Valeriy Glushkov wrote:
>> Hi Seth,
>>
>> It would be great if you send me a modified source with changes you need
>> or a patch and I add it to the SPDK build, reproduce the case and send  =

>> you
>> the resulting debug log.
>>
>> It seems that the Log page request is okay itself as there are many such
>> requests before in the log...
>>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk


	=




--===============4468332901066869662==--