Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Does SPDK have specific requirement for NVMe SSDs(device controller) to get it working in the best way?
Date: Mon, 25 Mar 2019 20:08:27 +0000	[thread overview]
Message-ID: <30adab4a373cba5b40d49771ffb14fdc288ef313.camel@intel.com> (raw)
In-Reply-To: MW2PR2101MB1113B54736388BE8120AFE37D55E0@MW2PR2101MB1113.namprd21.prod.outlook.com

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

On Mon, 2019-03-25 at 18:07 +0000, Liang Yang wrote:
> For example, how many I/O queue pairs, MSI-X messages, MDTS etc.

Most NVMe devices only need 1 I/O queue pair to get their full performance, but
that's ultimately up to the device. SPDK places no new requirements above what
the device requires.

SPDK does not use interrupts, so MSI-X is all disabled and doesn't matter.

SPDK will just automatically do the right thing for MDTS and optimal write size
and striping and all of that. You don't have to worry about it.

Thanks,
Ben


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


             reply	other threads:[~2019-03-25 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 20:08 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-26 18:24 [SPDK] Does SPDK have specific requirement for NVMe SSDs(device controller) to get it working in the best way? Harris, James R
2019-03-26 16:45 Liang Yang
2019-03-25 18:07 Liang Yang

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=30adab4a373cba5b40d49771ffb14fdc288ef313.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox