summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-write.txt
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2022-07-14 18:27:59 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2022-07-16 15:11:56 +0000
commit6197903bd42478987516bc4cc3f0769488a37065 (patch)
tree508d399340039960289dd1d96696db7c56c22321 /Documentation/nvme-write.txt
parentAdding upstream version 1.16. (diff)
downloadnvme-cli-6197903bd42478987516bc4cc3f0769488a37065.tar.xz
nvme-cli-6197903bd42478987516bc4cc3f0769488a37065.zip
Adding upstream version 2.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/nvme-write.txt')
-rw-r--r--Documentation/nvme-write.txt11
1 files changed, 8 insertions, 3 deletions
diff --git a/Documentation/nvme-write.txt b/Documentation/nvme-write.txt
index c48e6ae..4ac46e0 100644
--- a/Documentation/nvme-write.txt
+++ b/Documentation/nvme-write.txt
@@ -27,6 +27,7 @@ SYNOPSIS
[--dry-run | -w]
[--latency | -t]
[--storage-tag-check<storage-tag-check> | -C <storage-tag-check>]
+ [--force]
DESCRIPTION
-----------
@@ -114,9 +115,9 @@ metadata is passes.
-D <dsm>::
--dsm=<dsm>::
- The optional data set management attributes for this command. The
- argument for this is the lower 16 bits of the DSM field in a write
- command; the upper 16 bits of the field come from the directive
+ The optional data set management attributes for this command. The argument
+ for this is the least significant 8 bits of the DSM field in a write
+ command; the most significant 16 bits of the field come from the directive
specific field, if used. This may be used to set attributes for
the LBAs being written, like access frequency, type, latency,
among other things, as well as yet to be defined types. Please
@@ -142,6 +143,10 @@ metadata is passes.
This bit specifies the Storage Tag field shall be checked as part of end-to-end
data protection processing.
+--force::
+ Ignore namespace is currently busy and perfome the operation
+ even though.
+
EXAMPLES
--------
No examples yet.