From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============0384534424404338909=="
MIME-Version: 1.0
From: Harris, James R <james.r.harris at intel.com>
Subject: Re: [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target
Date: Wed, 06 Feb 2019 14:55:28 +0000
Message-ID: <EFA570CF-2774-4F71-A8B8-D3389F445952@intel.com>
In-Reply-To: op.zwr5tbdqns8zkg@sam8
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

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



=EF=BB=BFOn 2/6/19, 12:59 AM, "SPDK on behalf of Valeriy Glushkov" <spdk-bo=
unces(a)lists.01.org on behalf of valeriy.glushkov(a)starwind.com> wrote:

    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 lo=
ok  =

    at the issue...
    =

    Thank you for your help!


Hi Valeriy,

Can you provide detailed information about what your host module is doing t=
o induce this behavior?  Our tests with the Linux kernel host driver and th=
e SPDK host driver do not seem to be hitting this problem.

Thanks,

-Jim



--===============0384534424404338909==--