Multiple Connections per Session

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m (See also)
m (Standards compliance)
Line 10: Line 10:
== Standards compliance ==
== Standards compliance ==
-
The requirements as defined by RFC 3720 for non-[[ERL]] dependent MC/S support are not limited to the following:
+
The requirements as defined by RFC 3720 for non-[[Error Recovery Level|ERL]] dependent MC/S support are not limited to the following:
* Add additional connections on the fly with active+inactive IO (non-leading login)
* Add additional connections on the fly with active+inactive IO (non-leading login)

Revision as of 04:12, 31 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