All of lore.kernel.org
 help / color / mirror / Atom feed
From: olivier.mallinger@ip-maker.com (Olivier Mallinger - IP Maker)
Subject: IOCTL question.
Date: Fri, 30 Oct 2015 12:36:27 +0100	[thread overview]
Message-ID: <5633563B.3000901@ip-maker.com> (raw)

Hello.

I want to use the driver's ioctl and nvme cli with pass-through command 
to manage queues.
The purpose is to create a queue with Submission and completion PRP List.

I did a script doing the following :
   - Delete all submission queue (ex. : nvme admin-passthru /dev/nvme0 
--opcode=0x00 --cdw10=0x1)
   - Delete all completion queue (ex. : nvme admin-passthru /dev/nvme0 
--opcode=0x04 --cdw10=0x1)
  - Create new completion queue (ex. : nvme admin-passthru /dev/nvme0 
--opcode=0x05 --cdw10=0x3ff0001 --cdw11=0x2)
   - Create new submission queue (ex. : nvme admin-passthru /dev/nvme0 
--opcode=0x01 --cdw10=0x3ff0001 --cdw11=0x00010000)

Until now, the device has completed all the command successfully and is 
ready to perform I/O command with this new queue.

Then, i try to send a single write command (ex. : nvme write 
/dev/nvme0n1 -s 0 -c 0 -z 4096 -y 0 -r 0 -d essai.txt -p 0 -m 0 -a 0 -l 
0 -t 0 -f 0).
The device is never warn that a new command is available and the write 
is never fetch and not executed.

Can I manage the queue with the driver ioctl in that way ?
What is the driver behavior when I delete and create queue ?

Thanks.
Regards.
Olivier.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: olivier_mallinger.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20151030/d59a63c1/attachment.vcf>

             reply	other threads:[~2015-10-30 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 11:36 Olivier Mallinger - IP Maker [this message]
2015-10-30 13:38 ` IOCTL question 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=5633563B.3000901@ip-maker.com \
    --to=olivier.mallinger@ip-maker.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.