From f26f66d866ba1a9f3204e6fdfe2b07e67b5492ad Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Wed, 10 Apr 2024 21:41:32 +0200
Subject: Adding upstream version 2.8.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 Documentation/nvme-ocp-latency-monitor-log.txt | 44 ++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 Documentation/nvme-ocp-latency-monitor-log.txt

(limited to 'Documentation/nvme-ocp-latency-monitor-log.txt')

diff --git a/Documentation/nvme-ocp-latency-monitor-log.txt b/Documentation/nvme-ocp-latency-monitor-log.txt
new file mode 100644
index 0000000..a67c523
--- /dev/null
+++ b/Documentation/nvme-ocp-latency-monitor-log.txt
@@ -0,0 +1,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.
-- 
cgit v1.2.3