Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Content for v18.10.x
Date: Wed, 19 Dec 2018 21:36:45 +0000	[thread overview]
Message-ID: <5eb9d04d4d2917be23389054cb2e8073dff88630.camel@intel.com> (raw)
In-Reply-To: 435e9a40-f904-e517-d0ef-6dedcd7ea724@dev.mellanox.co.il

[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]

On Wed, 2018-12-19 at 20:11 +0200, Sasha Kotchubievsky wrote:
> Do you see the same pattern in both branches in "master" and in "18.10.1"?

Yes - as far as we've been able to tell it occurs in the same way on both master
and 18.10.1.

> > 
> > This is still an open issue, but Seth did figure out why we don't see the
> > problem on master - the test changed. The plan right now is to move forward
> > with
> > 18.10.1 without addressing this problem. 18.10.1 is far better than 18.10 in
> > this area already, and because this problem likely exists on master in the
> > same
> > form (and may not even ultimately be an SPDK problem), we'd rather not wait
> > to
> > get 18.10.1 out any longer.
> 
> Dose it mean, the patch fixing "ref count" will be merged into 18.10.1?

Yes, it's merged now.

> > 
> > Any assistance with investigating the root cause of the issue on the master
> > branch would be greatly appreciated. It replicates using the 18.10 version
> > of
> > the test/nvmf/lvol/nvmf_lvol.sh test, but not the version on master. The
> > problem
> > appears to be that the connection just drops, and both the initiator and the
> > target reactor to that correctly. But why the connection is dropping (it's
> > loopback) is the unknown.
> 
> Which SW stack is used in the testing: SoftROCE/MOFED/OFED? OS?
> 
> As I understand, for reproduction, I run test/nvmf/lvol/nvmf_lvol.sh  ( 
> from 18.10 ) on source coming from "master". Is that correct?

Correct, run the 18.10 version of the test against "master" and it will
eventually reproduce. It does not hit every time and we so far haven't gotten it
to happen on a development system, but we haven't run it very many times just
yet. We're testing on Fedora 28 with whatever RDMA stack it comes with natively
using a Mellanox RNIC in loopback.




             reply	other threads:[~2018-12-19 21:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 21:36 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-19 18:11 [SPDK] Content for v18.10.x Sasha Kotchubievsky
2018-12-19 17:25 Lance Hartmann ORACLE
2018-12-19 17:09 Walker, Benjamin
2018-12-17 18:37 Walker, Benjamin
2018-12-17 18:32 Sasha Kotchubievsky
2018-12-17 15:36 Harris, James R
2018-12-16 11:30 Sasha Kotchubievsky
2018-12-14 16:21 Harris, James R
2018-12-13 15:13 Sasha Kotchubievsky
2018-12-13 14:26 Harris, James R
2018-12-13  7:45 Sasha Kotchubievsky
2018-12-13  5:11 Zawadzki, Tomasz
2018-12-13  4:29 Sasha Kotchubievsky
2018-12-12 20:17 Zawadzki, Tomasz
2018-12-12 19:01 Sasha Kotchubievsky

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=5eb9d04d4d2917be23389054cb2e8073dff88630.camel@intel.com \
    --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