spdk.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Oza Oza <oza.oza at broadcom.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3
Date: Thu, 06 Apr 2017 21:20:24 +0530	[thread overview]
Message-ID: <12404c853237fc582aee8e049f9f471a@mail.gmail.com> (raw)
In-Reply-To: 8E9BB89F-7D7F-45E3-B386-43AE35186B02@intel.com

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

Ok thanks a lot Harris.

One last question:

Since SPDK doesn’t have multithread/multiple process support.

I try following.
Run couple of instance of fio on multiple disk in background.

But one of the fio_plugin process crashes saying:
No free hugepages reported
rte_panic("Cannot get hugepage information\n");

I do increase number of hugepages in kernel /proc/sys/vm/nr_hugepage
interface before running fio plugin.

Regards,
Oza.

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R
Sent: Thursday, April 06, 2017 12:23 AM
To: Storage Performance Development Kit
Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR***
Initialization timed out in state 3


> On Apr 4, 2017, at 9:00 PM, Oza Oza <oza.oza(a)broadcom.com> wrote:
>
> Also, couple of more questions.
>
> 1)  right now SPDK/fio_plugin doesnt support multiple threads right ?
> let us say I want to create multiple threads to push data in order to
> utilize all the cpus, then ? because I want to scale SPDK across cpu
> to effectively utilize it.

Currently the SPDK fio plugin only supports a single thread.  One of the
engineers here at Intel is actively working on multi-thread support.

>
> 2) the posted log in my previous mail:
> 	Why probing of spdk_nvme happens 3 times ? (rather multiple times ?)
> 	probe driver: 8086:953 spdk_nvme
> is it normal ?

Yes - this is normal.  These probe messages from DPDK are a bit misleading -
we are looking at modifying these to reduce confusion.

>
> Regards,
> Oza.
> -----Original Message-----
> From: Oza Oza [mailto:oza.oza(a)broadcom.com]
> Sent: Wednesday, April 05, 2017 9:04 AM
> To: 'Storage Performance Development Kit'
> Subject: RE: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init:
> ***ERROR*** Initialization timed out in state 3
>
> Ok, what is --thread=1 ?  (it means it will create one thread to
> handle the IO ?)

—thread implements each job as a thread (using pthread_create) instead of a
separate process.



-Jim

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2017-04-06 15:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 15:50 Oza Oza [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-07 18:14 [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3 Luse, Paul E
2017-08-07 17:58 Harris, James R
2017-08-07  5:43 Oza Oza
2017-04-18 12:03 Oza Oza
2017-04-06 17:20 Oza Oza
2017-04-05 18:52 Harris, James R
2017-04-05  8:57 Oza Oza
2017-04-05  5:14 Oza Oza
2017-04-05  4:00 Oza Oza
2017-04-05  3:33 Oza Oza
2017-04-04 15:39 Harris, James R
2017-04-04 14:18 Oza Oza
2017-04-04  9:24 Oza Oza
2017-04-03 15:42 Harris, James R
2017-04-03  9:01 Oza Oza

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=12404c853237fc582aee8e049f9f471a@mail.gmail.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;
as well as URLs for NNTP newsgroup(s).