summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-ocp-latency-monitor-log.txt
blob: a67c52378f052f01dd72b856738601c76ec2935b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
nvme-ocp-latency-monitor-log(1)
===============================

NAME
----
nvme-ocp-latency-monitor-log - Display latency monitor log page data in human
readable format

SYNOPSIS
--------
[verse]
'nvme ocp latency-monitor-log' <device> [--output-format=<fmt> | -o <fmt>]

DESCRIPTION
-----------

For the NVMe device given, latency monitor log page data.

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 OCP compliant 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 ocp latency-monitor-log /dev/nvme0
------------

NVME
----
Part of the nvme-user suite.