summaryrefslogtreecommitdiff
path: root/etc
diff options
context:
space:
mode:
authorMike Christie <michaelc@cs.wisc.edu>2010-02-12 22:59:34 -0600
committerMike Christie <michaelc@cs.wisc.edu>2010-03-22 17:32:08 -0500
commitcbb01e46eaa40a46e9f62871f17877e52b7fdc08 (patch)
tree3d1c299cf9bde22a9acde0ba6d2fcd242ca0fcca /etc
parent22610b42dea26f17d9be3f5bd23fed0f32436932 (diff)
downloadopen-iscsi-cbb01e46eaa40a46e9f62871f17877e52b7fdc08.tar.gz
iscsi tools: add MaxXmitDataSegmentLength param
This adds a MaxXmitDataSegmentLength param to iscsid.conf. It will limit the size of the pdu we send to the target. If you set it to 0, then we use the old behavior where we just use whatever the target requested. If you set it to a valid value then we use the min of the set value and what the target requested. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Diffstat (limited to 'etc')
-rw-r--r--etc/iscsid.conf9
1 files changed, 9 insertions, 0 deletions
diff --git a/etc/iscsid.conf b/etc/iscsid.conf
index 5fa0aca..e8f83fb 100644
--- a/etc/iscsid.conf
+++ b/etc/iscsid.conf
@@ -262,6 +262,15 @@ node.session.iscsi.MaxBurstLength = 16776192
# the default is 262144
node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
+# To specify the maximum number of data bytes the initiator will send
+# in an iSCSI PDU to the target, edit the following line.
+#
+# The value is the number of bytes in the range of 512 to (2^24-1).
+# Zero is a special case. If set to zero, the initiator will use
+# the target's MaxRecvDataSegmentLength for the MaxXmitDataSegmentLength.
+# The default is 0.
+node.conn[0].iscsi.MaxXmitDataSegmentLength = 0
+
# To specify the maximum number of data bytes the initiator can receive
# in an iSCSI PDU from a target during a discovery session, edit the
# following line.