Print this page
MFV: illumos-gate@48d370f1e98a10b1bdf160dd83a49e0f49f6c1b7
9809 nvme driver should attach to all NVMe 1.x devices
9810 Update parts of NVMe headers for newer specs
9811 nvmeadm(1M) should have ctf
Reviewed by: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Reviewed by: Jerry Jelinek <jerry.jelinek@joyent.com>
Reviewed by: Yuri Pankov <yuripv@yuripv.net>
Reviewed by: Richard Lowe <richlowe@richlowe.net>
Reviewed by: Andy Fiddaman <omnios@citrus-it.co.uk>
Approved by: Dan McDonald <danmcd@joyent.com>
Author: Robert Mustacchi <rm@joyent.com>
NEX-8020 illumos nvme changes
Reviewed by: Dan Fields <dan.fields@nexenta.com>
Reviewed by: Gordon Ross <gordon.ross@nexenta.com>
NEX-5192 Samsung SSD SM951-NVMe shows checksum errors
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef 'Jeff' Sipek <josef.sipek@nexenta.com>
NEX-5792 support NVMe namespace EUI64
Reviewed by: Josef 'Jeff' Sipek <josef.sipek@nexenta.com>
Reviewed by: Rick McNeal <rick.mcneal@nexenta.com>
NEX-6226 nvme(7d) manpage cleanup
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Jean McCormack <jean.mccormack@nexenta.com>
NEX-5791 support NVMe volatile write cache
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef 'Jeff' Sipek <josef.sipek@nexenta.com>
NEX-2182 need driver for Intel NVM Express (nvme) (preview)
Reviewed by: Dan Fields <dan.fields@nexenta.com>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man7d/nvme.7d.man.txt
+++ new/usr/src/man/man7d/nvme.7d.man.txt
1 1 NVME(7D) Devices NVME(7D)
2 2
3 3 NAME
4 4 nvme - Intel NVMe compliant storage driver
5 5
6 6 DESCRIPTION
7 7 The nvme driver uses the blkdev(7D) framework to provide access to Intel
8 8 NVMe compliant solid-state storage devices.
9 9
10 10 NVMe devices supporting multiple namespaces will present each namespace
|
↓ open down ↓ |
10 lines elided |
↑ open up ↑ |
11 11 as its own blkdev(7D) instance in the system.
12 12
13 13 CONFIGURATION
14 14 The nvme driver can be configured by defining properties in the nvme.conf
15 15 file. The parameters are considered an unstable interface, subject to
16 16 change without notice. The following properties are currently supported:
17 17
18 18 strict-version
19 19 This can be set to 0 to allow nvme to attach to devices
20 20 supporting newer version of the NVMe specification. The
21 - default value is 1, limiting nvme to work with devices up
22 - to specification version 1.2.
21 + default value is 1, limiting nvme to work with devices that
22 + support major version 1.
23 23
24 24 ignore-unknown-vendor-status
25 25 This can be set to 1 to allow nvme to continue operating
26 26 even if it receives an unknown vendor command status.
27 27
28 28 admin-queue-len
29 29 This is the number of entries in the admin command queue.
30 30 Legal values are between 16 and 4096, the default value is
31 31 256.
32 32
33 33 io-queue-len This is the number of entries in each I/O command queue.
34 34 Legal values are between 16 and 65536, the default value is
35 35 1024.
36 36
37 37 async-event-limit
38 38 This is the maximum number of asynchronous event requests
39 39 issued by the driver. Asynchronous events are used to
40 40 report error conditions. The driver will never use more
41 41 asynchronous events than this value, or what the hardware
42 42 supports if it is less, or 1/10th of the admin queue length
43 43 if it is less.
44 44
45 45 volatile-write-cache-enable
46 46 This property can be set to 0 to disable the volatile write
47 47 cache, if the hardware supports it. The default setting is
48 48 1, which enables the volatile write cache.
49 49
50 50 min-phys-block-size
51 51 This is the minimum physical block size that is reported to
52 52 blkdev(7d). This value must be a power of 2 greater than
53 53 or equal to 512. If the device reports a best block size
54 54 larger than what is specified here the driver will ignore
55 55 the value specified here.
56 56
57 57 FILES
58 58 /dev/dsk/cntnd0sn Block device minor nodes.
59 59 /dev/rdsk/cntnd0sn Raw block device minor nodes.
60 60
61 61 In the device minor nodes, the following substitutions may occur:
62 62
63 63 cn A controller number, typically one for each nvme
64 64 device found. Controller numbers are dynamically
65 65 assigned by the system.
66 66
67 67 tn The target number. This is the namespace EUI64 if
|
↓ open down ↓ |
35 lines elided |
↑ open up ↑ |
68 68 available, or the namespace ID used by the hardware.
69 69 Namespace ID 0 is reserved, hence target numbers
70 70 start with 1.
71 71
72 72 sn This is the slice number, representing a subset of
73 73 the disk. See dkio(7I).
74 74
75 75 SEE ALSO
76 76 blkdev(7D)
77 77
78 -illumos March 30, 2017 illumos
78 +illumos July 31, 2018 illumos
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX