Add documentation files for new Sandisk plugin commands.
Signed-off-by: jeff-lien-wdc <jeff.lien@sandisk.com>
linknvme:nvme-netapp-smdevices[1]::
Display information for each NVMe path to an E-Series volume
+linknvme:nvme-sndk-capabilities[1]::
+ Display Sandisk plugin command capabilities
+
+linknvme:nvme-sndk-clear-assert-dump[1]::
+ Clears the assert dump (if present)
+
+linknvme:nvme-sndk-clear-fw-activate-history[1]::
+ Clears the firmware activate history table
+
+linknvme:nvme-sndk-clear-pcie-correctable-errors[1]::
+ Clears the pcie correctable errors returned in the smart-log-add command
+
+linknvme:nvme-sndk-cloud-SSD-plugin-version[1]::
+ Display Sandisk plugin Cloud SSD Plugin Version
+
+linknvme:nvme-sndk-cloud-boot-SSD-version[1]::
+ Display Sandisk Cloud Boot SSD Version
+
+linknvme:nvme-sndk-drive-resize[1]::
+ Send NVMe Sandisk Resize Vendor Unique Command
+
+linknvme:nvme-sndk-get-drive-status[1]::
+ Send the NVMe Sandisk get-drive-status command
+
+linknvme:nvme-sndk-get-dev-capabilities-log[1]::
+ Display device capabilities og page data in human readable format
+
+linknvme:nvme-sndk-get-error-recovery-log[1]::
+ Display error recovery log page data in human readable format
+
+linknvme:nvme-sndk-get-latency-monitor-log[1]::
+ Display latency monitor log page data in human readable format
+
+linknvme:nvme-sndk-get-unsupported-reqs-log[1]::
+ Display unsupported requirements log page data in human readable format
+
+linknvme:nvme-sndk-log-page-directory[1]::
+ Retrieves the list of Log IDs supported by the drive
+
+linknvme:nvme-sndk-namespace-resize[1]::
+ Resizes the device's namespace
+
+linknvme:nvme-sndk-set-latency-monitor-feature[1]::
+ Set Latency Monitor feature
+
+linknvme:nvme-sndk-vs-cloud-log[1]::
+ Display the cloud log page
+
+linknvme:nvme-sndk-vs-device-waf[1]::
+ Display calculated device Write Amplication Factor
+
+linknvme:nvme-sndk-vs-drive-info[1]::
+ Send the NVMe Sandisk vs-drive-info command
+
+linknvme:nvme-sndk-vs-error-reason-identifier[1]::
+ Retrieve Sandisk device's telemetry log error reason identifier field
+
+linknvme:nvme-sndk-vs-fw-activate-history[1]::
+ Execute NVMe Sandisk vs-fw-activate-history Vendor Unique Command
+
+linknvme:nvme-sndk-vs-hw-rev-log[1]::
+ Display hardware revision log page
+
+linknvme:nvme-sndk-vs-internal-log[1]::
+ Retrieve Sandisk device's internal firmware log and save to file
+
+linknvme:nvme-sndk-vs-nand-stats[1]::
+ Send NVMe Sandisk vs-nand-stats Vendor Unique Command
+
+linknvme:nvme-sndk-vs-pcie-stats[1]::
+ Send the NVMe Sandisk vs-pcie-stats command
+
+linknvme:nvme-sndk-vs-smart-add-log[1]::
+ Send NVMe Sandisk smart add log Vendor Unique Command
+
+linknvme:nvme-sndk-vs-telemetry-controller-option[1]::
+ Disable/Enable the controller initiated option of the telemetry log page
+
+linknvme:nvme-sndk-vs-temperature-stats[1]::
+ Display temperature-related statistics
+
linknvme:nvme-toshiba-clear-pcie-correctable-errors[1]::
Reset the PCIe correctable errors count to zero
'nvme-show-regs',
'nvme-show-topology',
'nvme-smart-log',
+ 'nvme-sndk-capabilities',
+ 'nvme-sndk-clear-assert-dump',
+ 'nvme-sndk-clear-fw-activate-history',
+ 'nvme-sndk-clear-pcie-correctable-errors',
+ 'nvme-sndk-cloud-SSD-plugin-version',
+ 'nvme-sndk-cloud-boot-SSD-version',
+ 'nvme-sndk-drive-resize',
+ 'nvme-sndk-get-drive-status',
+ 'nvme-sndk-get-dev-capabilities-log',
+ 'nvme-sndk-get-error-recovery-log',
+ 'nvme-sndk-get-latency-monitor-log',
+ 'nvme-sndk-get-unsupported-reqs-log',
+ 'nvme-sndk-log-page-directory',
+ 'nvme-sndk-namespace-resize',
+ 'nvme-sndk-set-latency-monitor-feature',
+ 'nvme-sndk-vs-cloud-log',
+ 'nvme-sndk-vs-device-waf',
+ 'nvme-sndk-vs-drive-info',
+ 'nvme-sndk-vs-error-reason-identifier',
+ 'nvme-sndk-vs-fw-activate-history',
+ 'nvme-sndk-vs-hw-rev-log',
+ 'nvme-sndk-vs-internal-log',
+ 'nvme-sndk-vs-nand-stats',
+ 'nvme-sndk-vs-pcie-stats',
+ 'nvme-sndk-vs-smart-add-log',
+ 'nvme-sndk-vs-telemetry-controller-option',
+ 'nvme-sndk-vs-temperature-stats',
'nvme-solidigm-clear-fw-activate-history',
'nvme-solidigm-clear-pcie-correctable-errors',
'nvme-solidigm-cloud-SSDplugin-version',
--- /dev/null
+nvme-sndk-capabilities(1)
+=========================
+
+NAME
+----
+nvme-sndk-capabilities - Display sndk device command capabilities
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk capabilities' <device>
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, displays list of commands and support status.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+On success it returns 0, error code otherwise.
+
+EXAMPLES
+--------
+* Displays the capabilities for the device:
++
+------------
+# nvme sndk capabilities /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-clear-assert-dump(1)
+==============================
+
+NAME
+----
+nvme-sndk-clear-assert-dump - Clears the assert dump (if present).
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk clear-assert-dump' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, sends the sndk vendor unique clear assert
+dump command.
+
+The <device> parameter is mandatory and must be the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+The command will not be executed on devices that don't support it.
+
+OPTIONS
+-------
+None
+
+EXAMPLES
+--------
+* Clears the assert dump (if present):
++
+------------
+# nvme sndk clear-assert-dump /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite
--- /dev/null
+nvme-sndk-clear-fw-activate-history(1)
+======================================
+
+NAME
+----
+nvme-sndk-clear-fw-activate-history - Clears the firmware activate history table.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk clear-fw-activate-history' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, sends the sndk vendor unique clear fw activate
+history command.
+
+The <device> parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+OPTIONS
+-------
+None
+
+EXAMPLES
+--------
+* Clears the firmware activate history table:
++
+------------
+# nvme sndk clear-fw-activate-history /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite
--- /dev/null
+nvme-sndk-clear-pcie-correctable-errors(1)
+==========================================
+
+NAME
+----
+nvme-sndk-clear-pcie-correctable-errors - Clears the pcie correctable errors field returned in the smart-log-add command.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk clear-pcie-correctable-errors' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, sends the sndk vendor unique clear pcie
+correctable errors command.
+
+The <device> parameter is mandatory and may be either the NVMe
+character device (ex: /dev/nvme0), or a namespace block device (ex:
+/dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+OPTIONS
+-------
+None
+
+EXAMPLES
+--------
+* Clears the PCIe Correctable Error Count field returned in the smart-log-add command:
++
+------------
+# nvme sndk clear-pcie-correctable-errors /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite
--- /dev/null
+nvme-sndk-cloud-SSD-plugin-version(1)
+=====================================
+
+NAME
+----
+nvme-sndk-cloud-SSD-plugin-version - Display sndk plugin Cloud SSD Plugin Version
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk cloud-SSD-plugin-version' <device>
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, this command displays the current Cloud SSD
+Plugin Version (if supported by the device).
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+On success it returns 0, error code otherwise.
+
+EXAMPLES
+--------
+* Displays the cloud ssd plugin version for the device:
++
+------------
+# nvme sndk cloud-SSD-plugin-version /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-cloud-boot-SSD-version(1)
+===================================
+
+NAME
+----
+nvme-sndk-cloud-boot-SSD-version - Display sndk plugin Cloud Boot SSD Version
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk cloud-boot-SSD-version' <device>
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, this command displays the current Cloud Hyperscale
+Boot Version (if supported by the device).
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+On success it returns 0, error code otherwise.
+
+EXAMPLES
+--------
+* Displays the cloud boot ssd version for the device:
++
+------------
+# nvme sndk cloud-boot-SSD-version /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-drive-resize(1)
+=========================
+
+NAME
+----
+nvme-sndk-drive-resize - Send NVMe sndk Resize Vendor Unique Command,
+return result.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk drive-resize' <device> [--size=<sz> | -s <sz>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, sends a Vendor Unique sndk Resize command.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-s <sz>::
+--size=<sz>::
+ The new size (in GB) to resize the drive to.
+
+EXAMPLES
+--------
+* Has the program issue sndk Resize Vendor Unique Command :
++
+------------
+# nvme sndk drive-resize /dev/nvme0n1 --size=100
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-get-dev-capabilities-log(1)
+=====================================
+
+NAME
+----
+nvme-sndk-get-dev-capabilities-log - Send NVMe sndk get-dev-capabilities-log
+plugin command, return parsed log output
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk get-dev-capabilities-log' <device> [--output-format=<fmt> | -o <fmt>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a sndk plugin get-dev-capabilities-log command
+and output the device capabilities log data. The --output-format option will
+format the output as specified.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this log page.
+Results for any other device are undefined.
+
+On success it returns the parsed device capabilities log page data, error
+code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+EXAMPLES
+--------
+* Has the program issue sndk get-dev-capabilities-log plugin command :
++
+------------
+# nvme sndk get-dev-capabilities-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-get-drive-status(1)
+=============================
+
+NAME
+----
+nvme-sndk-get-drive-status - Send the NVMe sndk get-drive-status command, return
+result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk get-drive-status' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, send the unique sndk get-drive-status command and
+provide the additional drive status information.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+Output Explanation
+------------------
+[cols="2*", frame="topbot", align="center", options="header"]
+|===
+|Field |Description
+
+|*Percent Life Used.*
+|The percentage of drive function used.
+
+|*EOL (End of Life) Status*
+|The 3 possible states are : Normal, Read Only, or End of Life.
+
+|*Assert Dump Status*
+|The 2 possible states are : Present or Not Present.
+
+|*Thermal Throttling Status*
+|The 3 possible states are : Off, On, or Unavailable.
+
+|*Format Corrupt Reason*
+|The 3 possible states are : Not Corrupted, Corrupt due to FW Assert, or Corrupt for Unknown Reason.
+
+|===
+
+EXAMPLES
+--------
+* Has the program issue sndk get-drive-status command :
++
+------------
+# nvme sndk get-drive-status /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-get-error-recovery-log(1)
+===================================
+
+NAME
+----
+nvme-sndk-get-error-recovery-log - Send NVMe sndk get-error-recovery-log plugin
+command, return parsed log output.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk get-error-recovery-log' <device> [--output-format=<normal|json>
+-o <normal|json>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a sndk plugin get-error-recovery-log command
+and output the error recovery log data. The --output-format option will format
+the output as specified.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this log page.
+Results for any other device are undefined.
+
+On success it returns the parsed error recovery log page data, error
+code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+EXAMPLES
+--------
+* Has the program issue sndk get-error-recovery-log plugin command :
++
+------------
+# nvme sndk get-error-recovery-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-get-latency-monitor-log(1)
+====================================
+
+NAME
+----
+nvme-sndk-get-latency-monitor-log - Display latency monitor log page data in human readable format
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk get-latency-monitor-log' <device> [--output-format=<normal|json> -o <normal|json>]
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, latency monitor log page data.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this log page.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal' or 'json'. Only one output format
+ can be used at a time. The default is normal.
+
+EXAMPLES
+--------
+* Displays the get latency monitor log for the device:
++
+------------
+# nvme sndk get-latency-monitor-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-get-unsupported-reqs-log(1)
+=====================================
+
+NAME
+----
+nvme-sndk-get-unsupported-reqs-log - Send NVMe sndk get-unsupported-reqs-log
+plugin command, return parsed log output
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk get-unsupported-reqs-log' <device> [--output-format=<normal|json>
+-o <normal|json>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a sndk plugin get-unsupported-reqs-log command
+and output the unsupported requirements log data. The --output-format option
+will format the output as specified.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this log page.
+Results for any other device are undefined.
+
+On success it returns the parsed unsupported requirements log page data, error
+code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+EXAMPLES
+--------
+* Has the program issue sndk get-unsupported-reqs-log plugin command :
++
+------------
+# nvme sndk get-unsupported-reqs-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-log-page-directory(1)
+===============================
+
+NAME
+----
+nvme-sndk-log-page-directory - Retrieves the list of Log IDs supported by the drive
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk log-page-directory' <device> [--output-format=<normal|json|binary> -o <normal|json|binary>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, retrieves the log page directory which contains the list of
+log page IDs supported by the drive. The --output-format option will format the output as
+specified.
+
+The <device> parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns the log page directory information, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', 'json', or 'binary'. Only one output format
+ can be used at a time. The default is normal.
+
+EXAMPLES
+--------
+* sndk log-page-directory example command :
++
+------------
+# nvme sndk log-page-directory /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-namespace-resize(1)
+=============================
+
+NAME
+----
+nvme-sndk-namespace-resize - Resizes the device's namespace.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk namespace-resize' <device> [--nsid=<NAMESPACE ID>, -n <NAMSPACE ID>]
+ [--op_option=<OP OPTION>, -o <OP OPTION>]
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, sends the sndk Vendor Specific Command that modifies
+the namespace size reported the device.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+OPTIONS
+-------
+-n <NAMESPACE ID>::
+--namespace-id=<NAMESPACE_ID>::
+ Namespace ID; ID of the namespace to resize
+
+-o <OP OPTION>::
+--op-option=<OP OPTION>::
+ Overprovisioning Option; defaults to 0xF
+ Valid Values:
+ 0x1 - 7% of Original TNVMCAP reported value
+ 0x2 - 28% of Original TNVMCAP reported value
+ 0x3 - 50% of Original TNVMCAP reported value
+ 0xF - 0% of Original TNVMCAP reported value (original config)
+ All other values - reserved
+
+EXAMPLES
+--------
+* Resizes namespace 1 to 50% of the original TNVMCAP reported value:
++
+------------
+# nvme sndk namespace-resize /dev/nvme0 -n 1 -o 3
+------------
+* Resizes namespace 2 to 7% of the original TNVMCAP reported value:
++
+------------
+# nvme sndk namespace-resize /dev/nvme0 --namespace-id=2 --op-option=1
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-set-latency-monitor-feature(1)
+========================================
+
+NAME
+----
+nvme-sndk-set-latency-monitor-feature - Set NVMe sndk latency monitor feature options
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk set-latency-monitor-feature' <device>
+ [--active_bucket_timer_threshold=<NUM> | -t <NUM>]
+ [--active_threshold_a=<NUM> | -a <NUM>]
+ [--active_threshold_b=<NUM> | -b <NUM>]
+ [--active_threshold_c=<NUM> | -c <NUM>]
+ [--active_threshold_d=<NUM> | -d <NUM>]
+ [--active_latency_config=<NUM> | -f <NUM>]
+ [--active_latency_minimum_window=<NUM> | -w <NUM>]
+ [--debug_log_trigger_enable=<NUM> | -r <NUM>]
+ [--discard_debug_log=<NUM> | -l <NUM>]
+ [--latency_monitor_feature_enable=<NUM> | -e <NUM>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, this command set the
+latency monitor feature options (if supported by the device).
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+Setting results can be checked with 'get-latency-monitor-log' command.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-t <NUM>::
+--active_bucket_timer_threshold=<NUM>::
+ The value that loads the Active Bucket Timer Threshold; default value is 07E0h.
+
+-a <NUM>::
+--active_threshold_a=<NUM>::
+ The value that loads into the Active Threshold A; default value is 05h.
+
+-b <NUM>::
+--active_threshold_b=<NUM>::
+ The value that loads into the Active Threshold B; default value is 13h.
+
+-c <NUM>::
+--active_threshold_c=<NUM>::
+ The value that loads into the Active Threshold C; default value is 1Eh.
+
+-d <NUM>::
+--active_threshold_d=<NUM>::
+ The value that loads into the Active Threshold D; default value is 2Eh.
+
+-f <NUM>::
+--active_latency_config=<NUM>::
+ The value that loads into the Active Latency Configuration. This
+ configures how both the Active Latency Stamp, and the Active Measured
+ Latency Fields are updated on a per I/O command (Read, Write, Deallocate)
+ counter basis; default value is 0FFFh.
+
+-w <NUM>::
+--active_latency_minimum_window=<NUM>::
+ The value that loads into the Active Latency Minimum Window; default value is 0Ah.
+
+-r <NUM>::
+--debug_log_trigger_enable=<NUM>::
+ The value that loads into the Debug Log Trigger Enable; When set to 1b
+ the first time the bucket/counter combination is incremented a debug log
+ is triggered. When cleared to 0b a debug log will not be triggered when
+ the bucket/counter combination is incremented.
+
+-l <NUM>::
+--discard_debug_log=<NUM>::
+ Discard Debug Log. When cleared to 00h the debug log, if it exists, will
+ not be cleared. When set to 01h the debug log will be discarded so
+ another log can be triggered. All the fields in the Set Features Data
+ structure are valid. When set to 02h the debug log will be discarded so
+ another log can be triggered. None of the other fields of the Set
+ Features Data structure are valid.
+
+-e <NUM>::
+--latency_monitor_feature_enable=<NUM>::
+ Latency Monitor Feature Enable; When set to 01h the Latency Monitor
+ Feature is enabled. When cleared to 00h the Latency Monitor Feature is
+ disabled.
+
+EXAMPLES
+--------
+* Set NVMe sndk latency monitor feature options enabled with default value values:
++
+------------
+# nvme sndk set-latency-monitor-feature /dev/nvme0 -e 1
+------------
+* Set NVMe sndk latency monitor feature options disabled with default value values:
++
+------------
+# nvme sndk set-latency-monitor-feature /dev/nvme0 -e 0
+------------
+* Set NVMe sndk latency monitor feature options enabled with specific values:
++
+------------
+# nvme sndk set-latency-monitor-feature /dev/nvme0 --active_bucket_timer_threshold=1 \
+ --active_threshold_a=0x0 \
+ --active_threshold_b=0x1 \
+ --active_threshold_c=0x2 \
+ --active_threshold_d=0x3 \
+ --active_latency_config=0xfff \
+ --active_latency_minimum_window=0 \
+ --debug_log_trigger_enable=0 \
+ --discard_debug_log=0 \
+ --latency_monitor_feature_enable=0x1
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-cloud-log(1)
+=========================
+
+NAME
+----
+nvme-sndk-vs-cloud-log - Send NVMe sndk vs-cloud-log Vendor Unique Command, return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-cloud-log' <device> [--output-format=<normal|json> -o <normal|json>]
+ [--namespace-id=<nsid> | -n <nsid>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a Vendor Unique sndk vs-cloud-log command and
+provide the smart/health log.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+-n <nsid>::
+--namespace-id=<nsid>::
+ Sets the command's nsid value to the given nsid. Defaults to
+ 0xffffffff if not given. This option may not affect anything
+ depending on the log page, which may or may not be specific to
+ a namespace.
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-cloud-log Vendor Unique Command :
++
+------------
+# nvme sndk vs-cloud-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-device-waf(1)
+==========================
+
+NAME
+----
+nvme-sndk-vs-device-waf - Calculates the device write amplification factor and
+prints both TLC and SLC results
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-device-waf' <device> [--output-format=<normal|json> -o <normal|json>]
+ [--namespace-id=<nsid> | -n <nsid>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, calculates the device TLC and SLC write
+amplification factor.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+-n <nsid>::
+--namespace-id=<nsid>::
+ Sets the command's nsid value to the given nsid. Defaults to
+ 0xffffffff if not given. This option may not affect anything
+ depending on the log page, which may or may not be specific to
+ a namespace.
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-device-waf plugin Command :
++
+------------
+# nvme sndk vs-device-waf /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-drive-info(1)
+==========================
+
+NAME
+----
+nvme-sndk-vs-drive-info - Send the NVMe sndk vs-drive-info command, return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-drive-info' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, send the unique sndk vs-drive-info command and
+provide the additional drive information.
+
+The <device> parameter is mandatory and must be the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+Output Explanation
+------------------
+There are several different fields returned from this command depending
+on the drive:
+
+Drive HW Revision
+
+FTL Unit Size
+
+Customer Serial Number
+
+HyperScale Boot Version
+
+TCG Device Ownership
+
+EXAMPLE
+--------
+# nvme sndk vs-drive-info /dev/nvme0
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-error-reason-identifier(1)
+=======================================
+
+NAME
+----
+nvme-sndk-vs-error-reason-identifier - Retrieve sndk device's telemetry log error reason identifier field
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-error-reason-identifier' <device> [--log-id=<NUM>, -i <NUM>] [--file=<FILE>, -o <FILE>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, retrieve the telemetry log error reason id field for either the host generated or
+controller initiated log. The controller initiated telemetry log page option must be enabled to retrieve the
+error reason id for that log page id.
+
+The <device> parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-i <id>::
+--log-id=<id>::
+ Specifies the telemetry log id of the error reason identifier to retrieve.
+ Use id 7 for the host generated log page.
+ Use id 8 for the controller initiated log page.
+ The default is 7/host generated
+
+-o <FILE>::
+--output-file=<FILE>::
+ Output file; defaults to "<device serial number>_error_reason_identifier_host_<date>_<time>.bin" for
+ the host generated log or "<device serial number>_error_reason_identifier_ctlr_<date>_<time>.bin" for
+ the controller initiated log.
+
+EXAMPLES
+--------
+* Retrieves the host generated error reason identifier field and save it in file host_gen_error_reason_id.bin.
++
+--------
+# nvme sndk vs-error-reason-identifier /dev/nvme0 -i 7 -o host_gen_error_reason_id.bin
+--------
+* Retrieves the controller initiated error reason identifier field and save it in file ctlr_init_error_reason_id.bin.
++
+--------
+# nvme sndk vs-error-reason-identifier /dev/nvme0 -i 8 -o ctlr_init_error_reason_id.bin
+--------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-fw-activate-history(1)
+===================================
+
+NAME
+----
+nvme-sndk-vs-fw-activate-history - Execute NVMe sndk vs-fw-activate-history Vendor Unique Command, return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-fw-activate-history' <device> [--output-format=<normal|json> -o <normal|json>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, read a Vendor Unique sndk log page that returns the firmware activation
+history.
+
+The <device> parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+Firmware Activate History Log Page Data Output Explanation
+-----------------------------------------------------------
+[cols="2*", frame="topbot", align="center", options="header"]
+|===
+|Field |Description
+
+|*Entry Number*
+|The number of fw activate entry. The most recent 20 entries will be displayed.
+
+|*Power on Hour*
+|The time since the power on in hours:minutes:seconds.
+
+|*Power Cycle Count*
+|The power cycle count that the firmware activation occurred.
+
+|*Current Firmware*
+|The firmware level currently running on the SSD before the activation took place.
+
+|*New Firmware*
+|The new firmware level running on the SSD after the activation took place.
+
+|*Slot Number*
+|The slot that the firmware is being activated from.
+
+|*Commit Action Type*
+|The commit action type associated with the firmware activation event
+
+|*Result*
+|The result of the firmware activation event. The output shall be in the format:
+Pass or Failed + error code
+|===
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-fw-activate-history Vendor Unique Command :
++
+------------
+# nvme sndk vs-fw-activate-history /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-hw-rev-log(1)
+==========================
+
+NAME
+----
+nvme-sndk-vs-hw-rev-log - Send NVMe sndk vs-hw-rev-log Vendor Unique Command, return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-hw-rev-log' <device> [--output-format=<normal|json> | -o <normal|json>]
+ [--namespace-id=<nsid> | -n <nsid>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, retrieves and formats the Vendor Unique sndk hw revision log page.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+-n <nsid>::
+--namespace-id=<nsid>::
+ Sets the command's nsid value to the given nsid. Defaults to
+ 0xffffffff if not given. This option may not affect anything
+ depending on the log page, which may or may not be specific to
+ a namespace.
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-hw-rev-log plugin Command :
++
+------------
+# nvme sndk vs-hw-rev-log /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-internal-log(1)
+============================
+
+NAME
+----
+nvme-sndk-vs-internal-log - Retrieve sndk device's internal firmware log and save to file.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-internal-log' <device> [--output-file=<FILE>, -o <FILE>]
+ [--transfer-size=<SIZE>, -s <SIZE>]
+ [--data-area=<DATA AREA>, -d <DATA_AREA>]
+ [--file-size=<FILE SIZE>, -f <FILE SIZE>]
+ [--offset=<OFFSET>, -e <OFFSET>]
+ [--type=<TYPE>, -t <type>] [--verbose, -v]
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, sends the sndk Vendor Specific Internal Log request
+and saves the result to a file.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+OPTIONS
+-------
+-o <FILE>::
+--output-file=<FILE>::
+ Output file; defaults to device serial number followed by
+ "_internal_fw_log_<date>_<time>.bin" suffix
+
+-s <SIZE>::
+--transfer-size=<SIZE>::
+ Transfer size; defaults to 0x10000 (65536 decimal) bytes
+
+-d <DATA AREA>::
+--data-area=<DATA AREA>::
+ DUI data area to retrieve. The DUI data areas from 1 to <DATA AREA> will
+ be retrieved. This parameter is currently only supported on the SN340,
+ SN640, SN730, and SN840 devices.
+
+-f <FILE SIZE>::
+--file-size=<FILE SIZE>::
+ Specifies the desired size of the data file starting at the passed in
+ offset. This allows the user to retrieve the data in several smaller
+ files of the passed in size. This parameter is currently only supported
+ on the SN340 device.
+
+-e <OFFSET>::
+--offset=<OFFSET>::
+ Specifies the data offset at which to start retrieving the data. This
+ parameter is used in combination with the file size parameter to
+ retrieve the data in several smaller files. This parameter is currently
+ only supported on the SN340 device.
+
+-t <TYPE>::
+--type=<TYPE>::
+ Specifies the telemetry type - NONE, HOST, or CONTROLLER. This parameter
+ is used to get either the host generated or controller initiated
+ telemetry log page. If not specified or none is specified, the command
+ will return the default E6 log data. This parameter is currently only
+ supported on the SN640 and SN840 devices.
+
+-v <VERBOSE>::
+--verbose=<VERBOSE>::
+ Provides additional debug messages for certain drives.
+
+EXAMPLES
+--------
+* Gets the internal firmware log from the device and saves to default file in current directory (e.g. STM00019F3F9_internal_fw_log_20171127_095704.bin):
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0
+------------
+* Gets the internal firmware log from the device and saves to defined file in current directory (e.g. test.bin):
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0 -o test.bin
+------------
+* Gets the internal firmware log from the device and saves to defined file with pathname (e.g. /tmp/test):
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0 -o /tmp/test
+------------
+* Gets the internal firmware log from the device transferring the data in 64k chunks and saves to default file in current directory (e.g. STM00019F3F9_internal_fw_log_20171127_100754.bin):
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0 -s 0x10000
+------------
+* Gets the internal firmware log from the device transferring the data in 16k chunks and saves to default file in current directory (e.g. STM00019F3F9_internal_fw_log_20171127_100950.bin):
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0 -s 16384
+------------
+* Gets the internal firmware log up to data area 3 from the device in 3 files of 0x1000000 bytes:
++
+------------
+# nvme sndk vs-internal-log /dev/nvme0 -d 3 -f 0x1000000 -t 0x0000000 -o /tmp/sn340_dui_data_1.bin
+# nvme sndk vs-internal-log /dev/nvme0 -d 3 -f 0x1000000 -t 0x1000000 -o /tmp/sn340_dui_data_2.bin
+# nvme sndk vs-internal-log /dev/nvme0 -d 3 -f 0x1000000 -t 0x2000000 -o /tmp/sn340_dui_data_3.bin
+------------
+* Gets the host telemetry log page to data area 3 from the device and stores it in file host-telem-log-da3.bin:
++
+------------
+# nvme sndk vs-internal-log /dev/nvme1 -t host -o host-telem-log-da3.bin -d 3
+------------
+* Gets the controller telemetry log page to data area 3 from the device and stores it in file ctlr-telem-log-da3.bin:
++
+------------
+# nvme sndk vs-internal-log /dev/nvme1 -t controller -o ctlr-telem-log-da3.bin -d 3
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-nand-stats(1)
+==========================
+
+NAME
+----
+nvme-sndk-vs-nand-stats - Send NVMe sndk vs-nand-stats Vendor Unique Command, return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-nand-stats' <device> [--output-format=<normal|json> -o <normal|json>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a Vendor Unique sndk vs-nand-stats command and
+output the NAND statistics. The --output-format option will format the output as
+specified.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns the NAND statistics, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-nand-stats Vendor Unique Command :
++
+------------
+# nvme sndk vs-nand-stats /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-pcie-stats(1)
+==========================
+
+NAME
+----
+nvme-sndk-vs-pcie-stats - Send the NVMe sndk vs-pcie-stats command, return
+result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-pcie-stats' <device>
+
+DESCRIPTION
+-----------
+For the NVMe device given, send the unique sndk vs-pcie-stats command and
+return the pcie statistics data.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-pcie-stats command :
++
+------------
+# nvme sndk vs-pcie-stats /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-smart-add-log(1)
+=============================
+
+NAME
+----
+nvme-sndk-vs-smart-add-log - Send NVMe sndk vs-smart-add-log Vendor Unique Command,
+return result
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-smart-add-log' <device> [--interval=<NUM>, -i <NUM>]
+ [--output-format=<normal|json> -o <normal|json>]
+ [--log-page-version=<NUM>, -l <NUM>]
+ [--log-page-mask=<LIST>, -p <LIST>]
+ [--namespace-id=<nsid> | -n <nsid>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, send a Vendor Unique sndk vs-smart-add-log command and
+provide the additional smart log.
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-i <NUM>::
+--interval=<NUM>::
+ Return the statistics from specific interval, defaults to 14. This
+ parameter is only valid for the 0xC1 log page and ignored for all other
+ log pages.
+
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', or
+ 'json'. Only one output format can be used at a time.
+ Default is normal.
+
+-l <NUM>::
+--log-page-version=<NUM>::
+ Log Page Version: 0 = vendor, 1 = sndk. This parameter is only valid for
+ the 0xC0 log page and ignored for all other log pages.
+
+-p <LIST>::
+--log-page-mask=<LIST>::
+ Supply a comma separated list of desired log pages to display.
+ The possible values are 0xc0, 0xc1, 0xca, 0xd0.
+ Note: Not all pages are supported on all drives.
+ The default is to display all supported log pages.
+
+-n <nsid>::
+--namespace-id=<nsid>::
+ Sets the command's nsid value to the given nsid. Defaults to
+ 0xffffffff if not given. This option may not affect anything
+ depending on the log page, which may or may not be specific to
+ a namespace.
+
+Valid Interval values and description :-
+
+[cols="2*", frame="topbot", align="center", options="header"]
+|===
+|Value |Description
+
+|*1*
+|Most recent five (5) minute accumulated set.
+
+|*2-12*
+|Previous five (5) minute accumulated sets.
+
+|*13*
+|The accumulated total of sets 1 through 12 that contain the previous hour of
+accumulated statistics.
+
+|*14*
+|The statistical set accumulated since power-up.
+
+|*15*
+|The statistical set accumulated during the entire lifetime of the device.
+|===
+
+EXAMPLES
+--------
+* Has the program issue sndk vs-smart-add-log Vendor Unique Command with default interval (14) :
++
+------------
+# nvme sndk vs-smart-add-log /dev/nvme0
+------------
+* Has the program issue sndk vs-smart-add-log Vendor Unique Command for just the 0xCA log page :
++
+------------
+# nvme sndk vs-smart-add-log /dev/nvme0 -p 0xCA
+------------
+* Has the program issue sndk vs-smart-add-log Vendor Unique Command for 0xC0 and 0xCA log pages :
++
+------------
+# nvme sndk vs-smart-add-log /dev/nvme0 -p 0xCA,0xC0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-telemetry-controller-option(1)
+===========================================
+
+NAME
+----
+nvme-sndk-vs-telemetry-controller-option - Disable/Enable the controller
+initiated option of the telemetry log page.
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-telemetry-controller-option' <device>
+ [--disable, -d] [--enable, -e] [--status, -s]
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, sends the sndk Vendor Specific set feature command to
+disable, enable or get current status the controller initiated option of the
+telemetry log page.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+OPTIONS
+-------
+-d::
+--disable::
+ Disables the controller initiated option of the telemetry log page.
+
+-e::
+--enable::
+ Enables the controller initiated option of the telemetry log page.
+
+-s::
+--status::
+ Returns the current status (enabled or disabled) of the controller
+ initiated option of the telemetry log page.
+
+EXAMPLES
+--------
+* Disables the controller initiated option of the telemetry log page:
++
+------------
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 --disable
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 -d
+------------
+* Enables the controller initiated option of the telemetry log page:
++
+------------
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 --enable
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 -e
+------------
+* Gets the current status (enabled or disabled) of the controller initiated option of the telemetry log page:
++
+------------
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 --status
+# nvme sndk vs-telemetry-controller-option /dev/nvme0 -s
+------------
+
+NVME
+----
+Part of the nvme-user suite.
--- /dev/null
+nvme-sndk-vs-temperature-stats(1)
+=================================
+
+NAME
+----
+nvme-sndk-vs-temperature-stats - Display temperature-related statistics
+
+SYNOPSIS
+--------
+[verse]
+'nvme sndk vs-temperature-stats' <device>
+
+DESCRIPTION
+-----------
+
+For the NVMe device given, displays temperature statistics.
+
+The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
+
+This will only work on Sandisk devices supporting this feature.
+Results for any other device are undefined.
+
+Expected status and description :-
+
+[cols="2*", options="header"]
+|===
+|Statistic |Description
+
+|The current composite temperature
+|device temperature
+
+|Warning Composite TEMPerature threshold
+|temp of overheating
+
+|Critical Composite TEMPerature threshold
+|temp of critical overheating
+
+|Device Initiated Thermal Throttling support status
+|0 = unsupported, 1 = supported
+
+|Host Controlled Thermal Management support
+|0 = unsupported, 1 = supported
+
+|Thermal Management Temperature 1 (Light throttle)
+|temp to start light throttle
+
+|Thermal Management Temperature 1 Transition Counter
+|# times switched into light throttle
+
+|Thermal Management Temperature 1 Total Time
+|# seconds spent in light throttle
+
+|Thermal Management Temperature 2 (Heavy throttle)
+|temp to start heavy throttle
+
+|Thermal Management Temperature 2 Transition Counter
+|# times switched into heavy throttle
+
+|Thermal Management Temperature 2 Total Time
+|# seconds spent in heavy throttle
+
+|Thermal Shutdown Threshold
+|temp of device shutdown
+|===
+
+On success it returns 0, error code otherwise.
+
+EXAMPLES
+--------
+* Displays the temperature stats for the device:
++
+------------
+# nvme sndk vs-temperature-stats /dev/nvme0
+------------
+
+NVME
+----
+Part of the nvme-user suite.
#define SANDISK_PLUGIN_VERSION "2.12.0"
#include "cmd.h"
-PLUGIN(NAME("sandisk", "Sandisk vendor specific extensions", SANDISK_PLUGIN_VERSION),
+PLUGIN(NAME("sndk", "Sandisk vendor specific extensions", SANDISK_PLUGIN_VERSION),
COMMAND_LIST(
ENTRY("vs-internal-log", "Sandisk Internal Firmware Log",
sndk_vs_internal_fw_log)
projects / users / sagi / nvme-cli.git / commitdiff