path: root/Documentation/target
diff options
authorIlias Tsitsimpis <>2015-04-23 21:30:09 +0300
committerNicholas Bellinger <>2015-05-30 22:41:47 -0700
commite4648b014e03baee45d5f5146c1219b19e4e5f2f (patch)
tree652bf355631417eb402589d9a479454507d8c444 /Documentation/target
parentf97ec7db1606875666366bfcba8476f8c917db96 (diff)
target/user: Add support for bidirectional commands
Enable TCMU to handle bidirectional SCSI commands. In such cases, entries in iov[] cover both the Data-In and the Data-Out buffers. The first iov_cnt entries correspond to the Data-Out buffer, while the remaining iov_bidi_cnt entries correspond to the Data-In buffer. Signed-off-by: Ilias Tsitsimpis <> Signed-off-by: Vangelis Koukis <> Reviewed-by: Andy Grover <> Signed-off-by: Nicholas Bellinger <>
Diffstat (limited to 'Documentation/target')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/target/tcmu-design.txt b/Documentation/target/tcmu-design.txt
index 263b907517ac..bef81e42788f 100644
--- a/Documentation/target/tcmu-design.txt
+++ b/Documentation/target/tcmu-design.txt
@@ -152,7 +152,7 @@ overall shared memory region, not the entry. The data in/out buffers
are accessible via tht req.iov[] array. iov_cnt contains the number of
entries in iov[] needed to describe either the Data-In or Data-Out
buffers. For bidirectional commands, iov_cnt specifies how many iovec
-entries cover the Data-Out area, and iov_bidi_count specifies how many
+entries cover the Data-Out area, and iov_bidi_cnt specifies how many
iovec entries immediately after that in iov[] cover the Data-In
area. Just like other fields, iov.iov_base is an offset from the start
of the region.