Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: Testing IO PRP List
Date: Thu, 5 Mar 2015 15:12:57 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LNX.2.00.1503051451430.32385@localhost.lm.intel.com> (raw)
In-Reply-To: <54F867BD.6070806@ip-maker.com>

On Thu, 5 Mar 2015, Olivier Mallinger - IP Maker wrote:
> Continuing my investigation to test NVMe feature, I am looking for a way to 
> test IO PRP List.
>
> Basically, the driver only creates contiguous queue for both submission and 
> completion queues.
> To test, I wanted to use nvme-cli to do the following :
>  1 - Delete one IO submission queue using "admin-passthru" command
>  2 - Delete one IO completion queue using "admin-passthru" command
>  3 - Create one IO completion queue using "admin-passthru" command with 
> support of PRP List
>  4 - Create one IO submission queue using "admin-passthru" command with 
> support of PRP List
>  5 - Perform many IO read and write to check IO PRP List behavior

I don't think you should delete or create queues from userspace.
Deleting them out from under the driver is just going to confuse it
when IO stops working. Creating isn't safe since the user address for
the queue is pinned in memory only while the passthrough command is in
flight. Plus the queue memory is freed when the "nvme" program exits
anyway, but the h/w queue still exists.

The driver does not do any interpretation what-so-ever on passthroughs,
so while it is possible to send those commands, it's not going to do
what I think you're looking for.

There's no reason I know of to add support for physically discontiguous
IO queues in the Linux driver, so I don't think this feature is testable
in this environment.

  reply	other threads:[~2015-03-05 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 14:27 Testing IO PRP List Olivier Mallinger - IP Maker
2015-03-05 15:12 ` Keith Busch [this message]
2015-03-05 15:24   ` Olivier Mallinger - IP Maker
2015-03-05 15:30     ` Keith Busch

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=alpine.LNX.2.00.1503051451430.32385@localhost.lm.intel.com \
    --to=keith.busch@intel.com \
    /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