From: Valeriy Glushkov <valeriy.glushkov at starwind.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target
Date: Thu, 07 Feb 2019 15:37:30 +0000 [thread overview]
Message-ID: <op.zwuloox2ns8zkg@sam8> (raw)
In-Reply-To: 0500ca29-968c-7003-d0b5-66698f890606@dev.mellanox.co.il
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
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> писал(а) в своём письме
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
next reply other threads:[~2019-02-07 15:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 15:37 Valeriy Glushkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-28 22:07 [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target Valeriy Glushkov
2019-02-27 15:04 Howell, Seth
2019-02-27 15:00 Howell, Seth
2019-02-26 23:45 Lance Hartmann ORACLE
2019-02-26 22:21 Valeriy Glushkov
2019-02-07 18:18 Howell, Seth
2019-02-07 18:05 Sasha Kotchubievsky
2019-02-07 16:59 Howell, Seth
2019-02-07 14:31 Sasha Kotchubievsky
2019-02-07 4:50 Valeriy Glushkov
2019-02-06 23:06 Harris, James R
2019-02-06 23:03 Howell, Seth
2019-02-06 20:27 Howell, Seth
2019-02-06 18:15 Valeriy Glushkov
2019-02-06 16:54 Harris, James R
2019-02-06 16:03 Howell, Seth
2019-02-06 14:55 Harris, James R
2019-02-06 7:59 Valeriy Glushkov
2019-02-06 0:35 Harris, James R
2019-02-05 11:41 Valeriy Glushkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.zwuloox2ns8zkg@sam8 \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox