All of lore.kernel.org
 help / color / mirror / Atom feed
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, 28 Feb 2019 22:07:18 +0000	[thread overview]
Message-ID: <op.zxxzqaoxns8zkg@sam8> (raw)
In-Reply-To: EA913ED399BBA34AA4EAC2EDC24CDD009C272ED6@FMSMSX105.amr.corp.intel.com

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

Hi Seth,

Thank you for the update!
The NVMf target works for me now.

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

Howell, Seth <seth.howell(a)intel.com> писал(а) в своём письме Wed, 27 Feb  
2019 17:00:47 +0200:

> Hi Valeriy,
>
> This was a really stupid mistake on my part. I moved a decrement up  
> without moving the assert that accompanied it up with it (in my original  
> fix). Please see this one liner which should fix it. I will also  
> backport it to 19.01.1. The silver lining here is that there is nothing  
> functionally wrong with the code, the assert was just erroneous and will  
> hit when SPDK is built in debug mode.
>
> https://review.gerrithub.io/c/spdk/spdk/+/446440/1/lib/nvmf/rdma.c
>
> Thank you for replying and pointing this out,
>
> Seth
>
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Valeriy  
> Glushkov
> Sent: Tuesday, February 26, 2019 3:21 PM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: Re: [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target
>
> Hi Seth,
>
> It seems that some problem is still present in the nvmf target built  
> from the recent SPDK trunk.
> It crashes with dump under our performance test.
>
> ===========
> # Starting SPDK v19.04-pre / DPDK 18.11.0 initialization...
> [ DPDK EAL parameters: nvmf --no-shconf -c 0x1 --log-level=lib.eal:6
> --base-virtaddr=0x200000000000 --file-prefix=spdk_pid131804 ]
> EAL: No free hugepages reported in hugepages-2048kB
> EAL: 2 hugepages of size 1073741824 reserved, but no mounted hugetlbfs  
> found for that size
> app.c: 624:spdk_app_start: *NOTICE*: Total cores available: 1
> reactor.c: 233:_spdk_reactor_run: *NOTICE*: Reactor started on core 0
> rdma.c:2758:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x20002458d000
> length=4096
> rdma.c:2758:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x20002464b000
> length=4096
> rdma.c:2758:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x2000245ae000
> length=4096
> rdma.c:2786:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x20002457e000
> length=4096
> rdma.c:2758:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x20002457e000
> length=4096
> rdma.c:2786:spdk_nvmf_rdma_poller_poll: *ERROR*: data=0x2000245a8000
> length=4096
> nvmf_tgt: rdma.c:2789: spdk_nvmf_rdma_poller_poll: Assertion  
> `rdma_req->num_outstanding_data_wr > 0' failed.
> ^C
> [1]+  Aborted                 (core dumped) ./nvmf_tgt -c ./nvmf.conf
> =========
>
> Do you need the dump file or some additional info?
>
> --
> Best regards,
> Valeriy Glushkov
> www.starwind.com
> valeriy.glushkov(a)starwind.com
>

	



             reply	other threads:[~2019-02-28 22:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 22:07 Valeriy Glushkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-27 15:04 [SPDK] A problem with SPDK 19.01 NVMeoF/RDMA target 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  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.zxxzqaoxns8zkg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.