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: Wed, 06 Feb 2019 07:59:29 +0000 [thread overview]
Message-ID: <op.zwr5tbdqns8zkg@sam8> (raw)
In-Reply-To: 48D118FF-A7D9-4EDD-B2A6-2A78D1A5B1E7@intel.com
[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]
Hi Jim,
Our module is an implementation of the NVMeoF/RDMA host.
It works with SPDK 18.10.1 well, so the problem seems to be related to the
SPDK 19.01 code.
I can see that the RDMA request's state engine have been changed in the
recent SPDK release.
So it would be great if the author of the modifications could take a look
at the issue...
Thank you for your help!
--
Best regards,
Valeriy Glushkov
www.starwind.com
valeriy.glushkov(a)starwind.com
Harris, James R <james.r.harris(a)intel.com> писал(а) в своём письме Wed, 06
Feb 2019 02:35:38 +0200:
> Hi Valeriy,
>
> Can you provide more details on this test host module?
>
> Thanks,
>
> Jim
>
>> On Feb 5, 2019, at 4:41 AM, Valeriy Glushkov
>> <valeriy.glushkov(a)starwind.com> wrote:
>>
>> Hi All!
>>
>> It seems there is an issue in the 19.01 code that leads to a request
>> stays unanswered and our test NVMeoF/RDMA host module does not receive
>> the completion.
>>
>> From the debug log of the target:
>> =======
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 1
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 2
>> rdma.c:1414:spdk_nvmf_rdma_request_parse_sgl: *DEBUG*: Request
>> 0x1402a20 took 1 buffer/s from central pool
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 5
>> request.c: 121:nvmf_trace_command: *DEBUG*: Admin cmd: opc 0x02 fuse 0
>> cid 2751 nsid 4294967295 cdw10 0x001e0002
>> request.c: 127:nvmf_trace_command: *DEBUG*: psdt 0
>> request.c: 136:nvmf_trace_command: *DEBUG*: SGL: Keyed (Inv): addr
>> 0xffffb28f67223dd0 key 0x8294c len 0x200
>> ctrlr.c:1285:spdk_nvmf_ctrlr_get_log_page: *DEBUG*: Get log page:
>> LID=0x02 offset=0x0 len=0x7c
>> request.c: 92:spdk_nvmf_request_complete: *DEBUG*: cpl: cid=2751
>> cdw0=0x00000000 rsvd1=0 status=0x0000
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 7
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 8
>> rdma.c:1508:spdk_nvmf_rdma_request_process: *DEBUG*: Request 0x1402a20
>> entering state 8
>> ========
>>
>> The same host module works well with the SPDK 18.10.1 NVMf target.
>>
>> Is this a bug in the recent SPDK code?
>>
>> --
>> Best regards,
>> Valeriy Glushkov
>> www.starwind.com
>> valeriy.glushkov(a)starwind.com
>>
next reply other threads:[~2019-02-06 7:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 7:59 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 15:37 Valeriy Glushkov
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 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.zwr5tbdqns8zkg@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