summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-pred-lat-event-agg-log.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-24 07:57:54 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-24 07:57:54 +0000
commit66e4b69042cd3b44acd42f1fad2109180c1bc48b (patch)
tree8bd8e664ae856167566375357963062e8112f181 /Documentation/nvme-pred-lat-event-agg-log.html
parentReleasing debian version 2.5-1. (diff)
downloadnvme-cli-66e4b69042cd3b44acd42f1fad2109180c1bc48b.tar.xz
nvme-cli-66e4b69042cd3b44acd42f1fad2109180c1bc48b.zip
Merging upstream version 2.7.1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/nvme-pred-lat-event-agg-log.html')
-rw-r--r--Documentation/nvme-pred-lat-event-agg-log.html25
1 files changed, 13 insertions, 12 deletions
diff --git a/Documentation/nvme-pred-lat-event-agg-log.html b/Documentation/nvme-pred-lat-event-agg-log.html
index bead028..9acd37a 100644
--- a/Documentation/nvme-pred-lat-event-agg-log.html
+++ b/Documentation/nvme-pred-lat-event-agg-log.html
@@ -749,9 +749,10 @@ nvme-pred-lat-event-agg-log(1) Manual Page
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
-<pre class="content"><em>nvme pred-lat-event-agg-log</em> &lt;device&gt; [--log-entries=&lt;log_entries&gt; | -e &lt;log_entries&gt;]
+<pre class="content"><em>nvme pred-lat-event-agg-log</em> &lt;device&gt;
+ [--log-entries=&lt;log_entries&gt; | -e &lt;log_entries&gt;]
[--rae | -r] [--raw-binary | -b]
- [--output-format=&lt;fmt&gt; | -o &lt;fmt&gt;]</pre>
+ [--output-format=&lt;fmt&gt; | -o &lt;fmt&gt;] [--verbose | -v]</pre>
<div class="attribution">
</div></div>
</div>
@@ -782,11 +783,11 @@ another program to parse.</p></div>
</dt>
<dd>
<p>
- Retrieve the Predictable Latency Event Aggregate Log pending entries.
- This argument is mandatory and its success may depend on the device&#8217;s
- statistics to provide this log For More details see NVM Express 1.4 Spec.
- Section 5.14.1.11. The maximum number of log entries supported is 2044
- for the device.
+ Retrieve the Predictable Latency Event Aggregate Log pending entries.
+ This argument is mandatory and its success may depend on the device&#8217;s
+ statistics to provide this log For More details see NVM Express 1.4 Spec.
+ Section 5.14.1.11. The maximum number of log entries supported is 2044
+ for the device.
</p>
</dd>
<dt class="hdlist1">
@@ -812,15 +813,15 @@ another program to parse.</p></div>
</p>
</dd>
<dt class="hdlist1">
--o &lt;format&gt;
+-o &lt;fmt&gt;
</dt>
<dt class="hdlist1">
---output-format=&lt;format&gt;
+--output-format=&lt;fmt&gt;
</dt>
<dd>
<p>
- Set the reporting format to <em>normal</em>, <em>json</em>, or <em>binary</em>.
- Only one output format can be used at a time.
+ Set the reporting format to <em>normal</em>, <em>json</em>, or <em>binary</em>.
+ Only one output format can be used at a time.
</p>
</dd>
</dl></div>
@@ -863,7 +864,7 @@ Print the raw Predictable Latency Event Aggregate log to a file:
<div id="footer">
<div id="footer-text">
Last updated
- 2023-06-30 15:20:22 CEST
+ 2023-12-21 15:49:29 CET
</div>
</div>
</body>