Changes between Version 26 and Version 27 of NVMe_Support


Ignore:
Timestamp:
Nov 7, 2017, 6:51:50 PM (7 years ago)
Author:
Christian Franke
Comment:

Update NVMe support info for release 6.6

Legend:

Unmodified
Added
Removed
Modified
  • NVMe_Support

    v26 v27  
    2121||Linux 3.3 or later||  ✓  ||  ✓  ||[https://github.com/linux-nvme/nvme-cli nvme-cli], [https://github.com/xnox/nvme-user nvme-user] || ||
    2222||FreeBSD 9.2 or later||  ✓  ||  ✓  ||[https://www.freebsd.org/cgi/man.cgi?query=nvmecontrol nvmecontrol]|| ||
    23 ||NetBSD||  (✓)  ||  (✓)  || [http://netbsd.gw.com/cgi-bin/man-cgi/man?nvmectl+8+NetBSD-current nvmectl] ||NVMe support will be available in upcoming [https://www.netbsd.org/changes/changes-8.0.html#nvme%284%29 NetBSD 8.0]. Smartmontools supports this since r4343. ||
     23||NetBSD||  (✓)  ||  ✓  || [http://netbsd.gw.com/cgi-bin/man-cgi/man?nvmectl+8+NetBSD-current nvmectl] ||NVMe support will be available in upcoming [https://www.netbsd.org/changes/changes-8.0.html#nvme%284%29 NetBSD 8.0]. Smartmontools supports this since 6.6 (r4343). ||
    2424||OpenBSD 6.0 or later||  ✓  ||  -  || ?? || Does the [http://man.openbsd.org/?query=nvme&apropos=1 OpenBSD NVMe] driver provide NVMe pass-through functionality? ||
    25 ||OSX 10.10.3+ native NVMe support ||  ✓  ||  ✓  || ||Before release 10.13 only Apple-branded NVMe devices were supported, monitoring API is implemented (NVMeSMARTClient) but not documented. Limited NVMe support added in the [https://binaryfruit.com/drivedx DriveDx] app (commercial, closed source) and in the smartmontools since r4438.||
     25||OSX 10.10.3+ native NVMe support ||  ✓  ||  ✓  || ||Before release 10.13 only Apple-branded NVMe devices were supported, monitoring API is implemented (NVMeSMARTClient) but not documented. Limited NVMe support added in the [https://binaryfruit.com/drivedx DriveDx] app (commercial, closed source) and in the smartmontools since 6.6 (r4438).||
    2626||OSX with [http://www.macvidcards.com/nvme-driver.html MacVidCards NVMe driver] ||  ✓  ||  -  || nvme-cli tool distributed with the driver ||IOCTL format is not documented, driver is closed source and seems to be abandoned  ||
    2727||Oracle Solaris 11.2+||   ✓  ||  -  ||[https://docs.oracle.com/cd/E36784_01/html/E36871/nvmeadm-1m.html nvmeadm] ||Interface is not documented ||
     
    2929||Windows with [https://www.openfabrics.org/index.php/windows-nvm-express/nvm-express-subversion-repos.html OpenFabrics] compatible NVMe driver||   ✓  ||  ✓  || Various vendor specific tools || Devices are accessed via [https://svn.openfabrics.org/svnrepo/nvmewin/releases/IOCTL_Sample_App/ NVME_PASS_THROUGH] I/O-control. Successfully tested with NVMe drivers from Intel, OCZ/Toshiba and Samsung. Does not work with Intel RST drivers or Microsoft NVMe drivers. ||
    3030||Windows 7 to 2012.R2 with [https://support.microsoft.com/en-us/kb/2990941 Microsoft NVMe driver] ||  (✓)  ||  -  || ?? || Older Microsoft NVMe drivers [https://social.msdn.microsoft.com/Forums/en-US/bc138b94-da4b-4851-9778-cc63ab65077b/ do not provide a NVMe pass-through I/O-control]. ||
    31 ||Windows 10 with Microsoft NVMe driver (stornvme.sys) ||  ✓  ||  (✓)  || ?? || Access via [https://msdn.microsoft.com/en-us/library/windows/desktop/mt718131.aspx enhanced version of IOCTL_STORAGE_QUERY_PROPERTY] is supported since smartmontools r4348. ||
     31||Windows 10 with Microsoft NVMe driver (stornvme.sys) ||  ✓  ||  ✓  || ?? || Access via [https://msdn.microsoft.com/en-us/library/windows/desktop/mt718131.aspx enhanced version of IOCTL_STORAGE_QUERY_PROPERTY] is supported since smartmontools 6.6 (r4348). ||
    3232== Sample smartctl output ==
    3333Sample `smartctl -x` output: