Multiple Connections per Session

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m (Overview)
m
Line 1: Line 1:
-
'''Multiple Connections per Session''' ('''MC/S''') means using multiple communication paths in a single session ("I_T Nexus"). Architectural session command ordering is preserved across those communication paths.
+
'''Multiple (iSCSI) connections per (iSCSI) session''' ('''MC/S''') means creating multiple communication paths in a single session ("I_T Nexus"), i.e. across [http://en.wikipedia.org/wiki/TCP TCP], [http://en.wikipedia.org/wiki/SCTP SCTP] or [[ISCSI Extensions for RDMA|iSER]] & RCaP transport connections.
-
{{AdSense right}}
+
-
== Overview ==
+
-
'''Multiple iSCSI connections per iSCSI session''' ('''MC/S''') means creating multiple communication paths across [http://en.wikipedia.org/wiki/TCP TCP], [http://en.wikipedia.org/wiki/SCTP SCTP] or [[ISCSI Extensions for RDMA|iSER]] & RCaP connections. Session-wide command (CmdSN defined) ordering is preserved per RFC 3720 to ensure in-order delivery of tasks from an SCSI Initiator Port to an SCSI Target Port as defined by the SCSI Architecture Model, in which iSCSI provides the SCSI transport.
+
Architectural session command ordering is preserved across those communication paths. Session-wide architectural command ordering (defined by the <code>CmdSN</code>) is preserved per RFC 3720. This is to ensure in-order delivery of tasks from an SCSI Initiator Port to an SCSI Target Port as defined by the SCSI Architecture Model, in which iSCSI provides the SCSI transport.
== Linux Compatibility ==
== Linux Compatibility ==

Revision as of 02:17, 30 December 2010

Multiple (iSCSI) connections per (iSCSI) session (MC/S) means creating multiple communication paths in a single session ("I_T Nexus"), i.e. across TCP, SCTP or iSER & RCaP transport connections.

Architectural session command ordering is preserved across those communication paths. Session-wide architectural command ordering (defined by the CmdSN) is preserved per RFC 3720. This is to ensure in-order delivery of tasks from an SCSI Initiator Port to an SCSI Target Port as defined by the SCSI Architecture Model, in which iSCSI provides the SCSI transport.

Contents

Linux Compatibility

Standards compliance

The requirements as defined by RFC 3720 for non-ERL dependent MC/S support are not limited to the following:

See also

Template:AdSense See also

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense