From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5857445149613650425==" MIME-Version: 1.0 From: Oza Oza Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3 Date: Thu, 06 Apr 2017 22:50:07 +0530 Message-ID: In-Reply-To: 12404c853237fc582aee8e049f9f471a@mail.gmail.com List-ID: To: spdk@lists.01.org --===============5857445149613650425== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Can I use SPDK perf under exmaples to benchmark multiple SSDs ? Regards, Oza. -----Original Message----- From: Oza Oza [mailto:oza.oza(a)broadcom.com] Sent: Thursday, April 06, 2017 9:20 PM To: 'Storage Performance Development Kit' Subject: RE: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3 Ok thanks a lot Harris. One last question: Since SPDK doesn=E2=80=99t 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 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=3D1 ? (it means it will create one thread to > handle the IO ?) =E2=80=94thread implements each job as a thread (using pthread_create) inst= ead of a separate process. -Jim _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk --===============5857445149613650425==--