linux-toradex.git/include/uapi/linux/nvme.h, branch v3.17-rc4 Linux kernel for Apalis and Colibri modules NVMe: Define Log Page constants 2014-06-13T14:53:49+00:00 Matthew Wilcox matthew.r.wilcox@intel.com 2014-06-13T14:53:49+00:00 3d69bb6e4699251102dc145b7800dd012ddec375 Taken from the 1.1a version of the spec Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Taken from the 1.1a version of the spec

Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Update data structures for NVMe 1.2 2014-06-03T15:29:31+00:00 Matthew Wilcox matthew.r.wilcox@intel.com 2014-05-10T02:45:08+00:00 23372af15e638bf3ce0764554db3b5e58bf7ceb8 Include changes from the current set of ratified Technical Proposals for NVMe 1.2. Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Include changes from the current set of ratified Technical Proposals
for NVMe 1.2.

Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Update namespace and controller identify structures to the 1.1a spec 2014-05-09T22:50:53+00:00 Dimitri John Ledkov dimitri.ledkov@canonical.com 2014-05-07T19:55:30+00:00 f2727f7eb9132803d06309839a95de3dad82d237 Controller: add CNTLID, AVSCC, APSTA, NVSCC, ACWU, SGLS fields. Namespace: add NMIC, RESCAP, EUI64 fields. EUI64 is specifically interesting, since it can be used to construct an UEFI NVMe device path for a boot entry. As per NVM Express 1.1a spec: http://www.nvmexpress.org/wp-content/uploads/NVM-Express-1_1a.pdf Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com> Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Controller: add CNTLID, AVSCC, APSTA, NVSCC, ACWU, SGLS fields.

Namespace: add NMIC, RESCAP, EUI64 fields. EUI64 is specifically
interesting, since it can be used to construct an UEFI NVMe device
path for a boot entry.

As per NVM Express 1.1a spec:
http://www.nvmexpress.org/wp-content/uploads/NVM-Express-1_1a.pdf

Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Configure support for block flush 2014-05-05T14:53:53+00:00 Keith Busch keith.busch@intel.com 2014-04-29T17:41:28+00:00 a7d2ce2832d84e0182585f63bf96ca7323b3aee7 This configures an nvme request_queue as flush capable if the device has a volatile write cache present. Signed-off-by: Keith Busch <keith.busch@intel.com> Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
This configures an nvme request_queue as flush capable if the device
has a volatile write cache present.

Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Update copyright headers 2014-05-05T14:41:25+00:00 Matthew Wilcox matthew.r.wilcox@intel.com 2014-04-11T14:37:39+00:00 8757ad65d30f009fe0beeb2d70d3cd834cb998f2 Make the copyright dates accurate and remove the final paragraph that includes the address of the FSF. Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Make the copyright dates accurate and remove the final paragraph that
includes the address of the FSF.

Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Retry failed commands with non-fatal errors 2014-04-10T21:11:59+00:00 Keith Busch keith.busch@intel.com 2014-04-03T22:45:23+00:00 edd10d33283899fb15d99a290dcc9ceb3604ca78 For commands returned with failed status, queue these for resubmission and continue retrying them until success or for a limited amount of time. The final timeout was arbitrarily chosen so requests can't be retried indefinitely. Since these are requeued on the nvmeq that submitted the command, the callbacks have to take an nvmeq instead of an nvme_dev as a parameter so that we can use the locked queue to append the iod to retry later. The nvme_iod conviently can be used to track how long we've been trying to successfully complete an iod request. The nvme_iod also provides the nvme prp dma mappings, so I had to move a few things around so we can keep those mappings. Signed-off-by: Keith Busch <keith.busch@intel.com> [fixed checkpatch issue with long line] Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
For commands returned with failed status, queue these for resubmission
and continue retrying them until success or for a limited amount of
time. The final timeout was arbitrarily chosen so requests can't be
retried indefinitely.

Since these are requeued on the nvmeq that submitted the command, the
callbacks have to take an nvmeq instead of an nvme_dev as a parameter
so that we can use the locked queue to append the iod to retry later.

The nvme_iod conviently can be used to track how long we've been trying
to successfully complete an iod request. The nvme_iod also provides the
nvme prp dma mappings, so I had to move a few things around so we can
keep those mappings.

Signed-off-by: Keith Busch <keith.busch@intel.com>
[fixed checkpatch issue with long line]
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Abort timed out commands 2014-01-28T00:27:53+00:00 Keith Busch keith.busch@intel.com 2013-12-10T20:10:38+00:00 c30341dc3c436cf43508cd44cdfbb3810c38c195 Send nvme abort command to io requests that have timed out on an initialized device. If the command is not returned after another timeout, schedule the controller for reset. Signed-off-by: Keith Busch <keith.busch@intel.com> [fix endianness issues] Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Send nvme abort command to io requests that have timed out on an
initialized device. If the command is not returned after another timeout,
schedule the controller for reset.

Signed-off-by: Keith Busch <keith.busch@intel.com>
[fix endianness issues]
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Update nvme_id_power_state with latest spec 2013-09-03T20:32:26+00:00 Keith Busch keith.busch@intel.com 2013-06-25T21:15:23+00:00 685585c25e8269cc355b59d1cd6fc65b8c5c4878 Signed-off-by: Keith Busch <keith.busch@intel.com> Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
NVMe: Split header file into user-visible and kernel-visible pieces 2013-09-03T20:32:25+00:00 Matthew Wilcox matthew.r.wilcox@intel.com 2013-06-25T19:14:56+00:00 42c7768316905dc64ad22256d6cbff273e3fbf55 To build user programs that call the NVMe ioctls, we need to have a user header file. Catch up to the new way of doing that by splitting the header file into kernel and uapi portions. Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> 
To build user programs that call the NVMe ioctls, we need to have a
user header file.  Catch up to the new way of doing that by splitting
the header file into kernel and uapi portions.

Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>