Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Sreeni (Sreenivasa) Busam (Stellus) <s.busam at stellus.com>
To: spdk@lists.01.org
Subject: [SPDK] Regarding NVMe driver command queue depth.
Date: Thu, 16 Nov 2017 19:25:42 +0000	[thread overview]
Message-ID: <67acc8057cd24c0f8d67926f9f39967d@stellus.com> (raw)
In-Reply-To: CGME20171116192543uscas1p133a58cadd1606d31d0e8d40e151860c4@uscas1p1.samsung.com

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

Hi Paul,

I was reading about the driver from SPDK site, and interested in understanding the queue depth for a device.
"The specification allows for thousands, but most devices support between 32 and 128. The specification makes no guarantees about the performance available from each queue pair, but in practice the full performance of a device is almost always achievable using just one queue pair. For example, if a device claims to be capable of 450,000 I/O per second at queue depth 128, in practice it does not matter if the driver is using 4 queue pairs each with queue depth 32, or a single queue pair with queue depth 128"
When queue depth is mentioned for device, is it the number of commands that can be issued from application to controller, and outstanding at any time?
Is there NVMe driver API to set the queue depth? Is my understanding correct if I think that the size of queue is at firmware level?
Please give some detail about the parameter.

Thanks,
Sreeni

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3191 bytes --]

             reply	other threads:[~2017-11-16 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 19:25 Sreeni Busam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-16 23:57 [SPDK] Regarding NVMe driver command queue depth Sreeni Busam
2017-11-17  0:04 Luse, Paul E
2017-11-17  0:59 Sreeni Busam
2017-11-17 16:44 Harris, James R
2017-11-17 18:52 Sreeni Busam
2017-11-17 19:02 Luse, Paul E
2017-11-17 20:18 Sreeni Busam
2017-11-20 20:50 Sreeni Busam

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=67acc8057cd24c0f8d67926f9f39967d@stellus.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