All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] NVMeF Taget Setup
Date: Wed, 01 Mar 2017 20:45:23 +0000	[thread overview]
Message-ID: <1488401121.9792.29.camel@intel.com> (raw)
In-Reply-To: 738fdd6f6a733e765aee80b4075064aa@cs.fsu.edu

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

Try deleting the [Nvme] section from your configuration file. This is a
 known bug with direct mode that will be fixed shortly.

On Wed, 2017-03-01 at 15:30 -0500, yzhu wrote:
> Hi all,
> 
> I got an error when trying to set up the NVMeF Target. The error
> says 
> "could not found NVMe controller at PCI address xxxxx". However, I
> do 
> have a NVMe drive with our system. I was wondering if someone has an 
> idea about this. I attached my configuration and error I got below.
> 
> 1. Configuration
> # Direct controller
> [Subsystem1]
>    NQN nqn.2016-06.io.spdk:cnode1
>    Core 0
>    Mode Direct
>    Listen RDMA 10.10.16.10:4420
>    Host nqn.2016-06.io.spdk:init
>    NVMe 0000:04:00.0
> 
> 
> 2. Error
> Starting Intel(R) DPDK initialization ...
> [ DPDK EAL parameters: nvmf -c 1 --file-prefix=spdk12027 
> --base-virtaddr=0x1000000000 --proc-type=auto ]
> EAL: Detected 40 lcore(s)
> EAL: Auto-detected process type: PRIMARY
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:953 spdk_nvme
> Occupied cpu core mask is 0x1
> Occupied cpu socket mask is 0x1
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:953 spdk_nvme
> Ioat Copy Engine Offload Enabled
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:953 spdk_nvme
> Probing device 0000:04:00.0
> Total cores available: 1
> Reactor started on core 0 on socket 0
> *** RDMA Transport Init ***
> allocated subsystem nqn.2014-08.org.nvmexpress.discovery on lcore 0
> on 
> socket 0
> allocated subsystem nqn.2016-06.io.spdk:cnode1 on lcore 0 on socket 0
> Subsystem nqn.2016-06.io.spdk:cnode1 is configured to run on a CPU
> core 
> 0 belonging to a different NUMA node than the associated NIC. This
> may 
> result in reduced performance.
> The NIC is on socket 1
> The Subsystem is on socket 0
> conf.c: 565:spdk_nvmf_construct_subsystem: ***ERROR*** Could not
> find 
> NVMe controller at PCI address 0000:04:00.0
> nvmf_tgt.c: 336:spdk_nvmf_startup: ***ERROR***
> spdk_nvmf_parse_conf() 
> failed
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:953 spdk_nvme
> EAL: Requested device 0000:04:00.0 cannot be used
> 
> Thanks in advance,
> Yue
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]

             reply	other threads:[~2017-03-01 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 20:45 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-02 17:52 [SPDK] NVMeF Taget Setup Walker, Benjamin
2017-03-02 17:37 yzhu
2017-03-01 20:30 yzhu

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=1488401121.9792.29.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 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.