From: Ramaraj Pandian <nr.pandian at samsung.com>
To: spdk@lists.01.org
Subject: [SPDK] NvmeOverTcp running with block size
Date: Wed, 23 Jan 2019 19:01:16 +0000 [thread overview]
Message-ID: <a761f62e9e80434bb84634536ff20099@samsung.com> (raw)
In-Reply-To: CGME20190123190117uscas1p103be0725af9e447b9d20eef2ac039dc0@uscas1p1.samsung.com
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi,
I am trying to ro perf with block size 64k and get this error, is there any configuration setup I am missing? Its works upto 8k block though.
Associating SPDK bdev Controller (SPDK00000000000001 ) with lcore 0
Initialization complete. Launching workers.
Starting thread on core 0
nvme_tcp.c: 909:nvme_tcp_pdu_ch_handle: *ERROR*: Expected PDU header length 24, got 7
nvme_tcp.c:1588:nvme_tcp_qpair_process_completions: *ERROR*: Error polling CQ! (11): Resource temporarily unavailable
Segmentation fault
Thanks
Ram
next reply other threads:[~2019-01-23 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 19:01 Ramaraj Pandian [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 23:21 [SPDK] NvmeOverTcp running with block size Yang, Ziye
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=a761f62e9e80434bb84634536ff20099@samsung.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