diff --git a/qla2x00t/qla2x00-target/README b/qla2x00t/qla2x00-target/README index 731208a22..b91479600 100644 --- a/qla2x00t/qla2x00-target/README +++ b/qla2x00t/qla2x00-target/README @@ -17,6 +17,14 @@ Linux kernel 2.6.26 and higher. Sorry, kernels below 2.6.26 are not supported, because it's too hard to backport used initiator driver to older kernels. +NPIV is particulary supported by this driver. You can create virtual +targets using standard Linux interface by echoing wwpn:wwnn into +/sys/class/fc_host/hostX/vport_create and work with them, but SCST core +will not see those virtual targets and, hence, provide the +target-oriented access control for them. However, the initiator-oriented +access control will still work very well. Note, you need NPIV-supporting +firmware as well as NPIV-supporting switches to use NPIV. + The original initiator driver was taken from the kernel 2.6.26. See also "ToDo" file for list of known issues and unimplemented @@ -82,6 +90,8 @@ You can find some installation and configuration HOWTOs in http://scst.sourceforge.net/qla2x00t-howto.html and https://forums.openfiler.com/viewtopic.php?id=3422. +It is recommended to use firmware version 5.x.x or higher. + Explicit conformation --------------------- diff --git a/qla2x00t/qla2x00-target/ToDo b/qla2x00t/qla2x00-target/ToDo index 97d152cc6..6a113aa65 100644 --- a/qla2x00t/qla2x00-target/ToDo +++ b/qla2x00t/qla2x00-target/ToDo @@ -1,7 +1,8 @@ Known issues and unimplemented features --------------------------------------- - - NPIV support + - Complete NPIV support. Particularly, SCST core should see all the virtual + targets and provide separate target-oriented access control for them. - If a Linux initiator asks for devices using INQUIRY command too soon before the controller on the 23xx target is fully initialized in the @@ -21,5 +22,5 @@ Known issues and unimplemented features and then read it with bs

Features comparison between Linux SCSI targets

-

As on August 2009

+

As on October 2009

@@ -147,22 +147,21 @@ any target reconfiguration in a PnP-like fashion) +SCSI requirements 12 +13 + + 14 + 15 @@ -237,18 +236,18 @@ ORDERED commands + 17 @@ -318,13 +317,13 @@ devices +reinstatement 20 - + + 15
+ - < (Windows 2003 clustering) + + + +
Safe RESERVE/RELEASE implementation according to -SCSI requirements 12 Safe Safe Not safe - - 13 Not safe Safe Safe Safe from + v1.4.18 Not safe
Safe implementation of Task Management commands -14 Safe Not safe Not safe Not safe Safe Not safe Not safe Not safe
Support for SCSI task attributes, including ORDERED commands + + -,
data corruption possible - - 15		 -,
data + + 14		 -,
data corruption possible - - 15
Persistent Reservations
@@ -180,7 +179,7 @@ ORDERED commands		 + + -,
data
SCSI MIBs - - - +- - 16
Cluster Storage Integration - - - VHACS + + -,
data
SCSI pass-through - 17 + Disks only, single + 16 + Disks only, single initiator only, not enforced - 18 + 17 - Single initiator only, not enforced - 18
Zero-copy data read/write to/from backstorage BLOCKIO, user space FILEIO in O_DIRECT mode, pass-through - 19 + 18 - 8 BLOCKIO BLOCKIO, pass- @@ -291,7 +290,7 @@ devices - Experimental - -
Zero-copy data send/receive Send only - 20 + 19 None 8 Send only Send only - Experimental - - + - - -
Safe implementation of connections and sessions -reinstatement 21 Safe Not safe Not safe Not safe Safe Not safe Not safe Not safe
Safe restart 22 Safe ? Not safe ? Safe restart 21 Safe ? Not safe ?
iSCSI MIBs - - - +- - 16
@@ -377,11 +376,7 @@ reinstatement 21 Safe Not s community forum by someone working for VMware. But, sure, it can affect not only VMware, but also any other cluster implementation, relying on this functionality.

-

13. The problem in IET - - was confirmed in IET mailing list.

- -

14. After a task management command completed and before the corresponding response was sent to the initiator, who sent that task management +

13. After a task management command completed and before the corresponding response was sent to the initiator, who sent that task management command, all the affected SCSI commands must get into a state, where they can't affect following after the tasks management response commands from this initiator. This is the safe implementation. The unsafe implementation only marks all the affected @@ -391,35 +386,35 @@ reinstatement 21 Safe Not s SCSI command, which initiator will send after it received the task management response thinking that all the aborted commands actually fully aborted. This could lead to a data corruption.

-

15. Both IET and LIO report in INQUIRY command response support for full task management model. But they process ORDERED +

14. Both IET and LIO report in INQUIRY command response support for full task management model. But they process ORDERED commands the same way as SIMPLE commands, i.e. allow free reorder of them before they get executed. That violates SCSI standard and can lead to a data corruption to any application relying on commands order provided by ORDERED attribute.

-

16. LIO exports the information needed for an RFC 4455 implementation, but requires additional RFC 4455 implementing module. +

15. LIO exports the information needed for an RFC 4455 implementation, but requires additional RFC 4455 implementing module. At the moment, there is no open source implementation of such module.

-

17. SCSI pass-through mode allows to export your local SCSI-capable device. For instance with it you can share your parallel +

16. SCSI pass-through mode allows to export your local SCSI-capable device. For instance with it you can share your parallel SCSI tape or SATA DVD-RW device to your iSCSI network.

-

18. STGT and LIO don't emulate all the necessary SCSI host functionality to allow to share SCSI devices +

17. STGT and LIO don't emulate all the necessary SCSI host functionality to allow to share SCSI devices in pass-through mode to several initiators. They can only pass SCSI commands from initiators to SCSI devices and responses back. This is safe only with a single initiator. This limitation isn't enforced anyhow and both STGT and LIO don't issue any warning about it, so an user will not be notified about this limitation and can quietly corrupt his/her data. You can find more technical information about it here.

-

19. You can find a proposal how to implement zero-copy FILEIO in SCST on the +

18. You can find a proposal how to implement zero-copy FILEIO in SCST on the Contributing page.

-

20. Doesn't need any kernel patch, except in the case, when used with user space backend.

+

19. Doesn't need any kernel patch, except in the case, when used with user space backend.

-

21. Connections and sessions reinstatement is, basically, a kind of Task Management command, because it implies commands aborting. +

20. Connections and sessions reinstatement is, basically, a kind of Task Management command, because it implies commands aborting. For instance, open-iscsi uses it as a less intrusive substistute for target reset in eh_target_reset_handler() callback. So, similarly to the safe task management above, a safe implementation of connections and sessions reinstatement must not accept SCSI commands from new connection/session until all the SCSI commands in being reinstated connection/session get into a state, where they can't affect new commands.

-

22. "Safe restart" means that after the iSCSI target restart, all the connected initiators will seamlessly restore all existing before +

21. "Safe restart" means that after the iSCSI target restart, all the connected initiators will seamlessly restore all existing before the restart connections. "Not safe" means that, most likely, the connected initiators will fail to restore existing connections with some errors. However, your iSCSI initiator also should be able to handle the safe restart. For instance, old (pre-CentOS/RHEL 5) open-iscsi has problems in this area. But the latest versions do it pretty well.

diff --git a/www/target_iscsi.html b/www/target_iscsi.html index 41d5f8c7e..4a02ec260 100644 --- a/www/target_iscsi.html +++ b/www/target_iscsi.html @@ -93,18 +93,17 @@ -
  • ISCSI-SCST has many code improvements and cleanups, including stability - and iSCSI RFC violations fixes. +
  • ISCSI-SCST has many code improvements and cleanups, including stability + and iSCSI RFC violations fixes. IET works well on "fast" paths and regularly used code branches, but in many corner cases it has various problems, from simply ignoring error processing, as it is for memory allocations, and crashing itself with BUG() macro, as it is for malformed packets from initiators, to possible data - corruption. See, for instance, this - thread on a VMware forum about in which Russian roulette IET users play using it with VMware.
    • + corruptions, because of, for instance, unsafe task management or sessions reinstatement implementations.
  • Due to reworked I/O architecture and SCST backend iSCSI-SCST has much - better performance in many cases and has potential for future improvements, like zero-copy - with Linux cache FILEIO. In many tests iSCSI-SCST outperforms tuned for best - performance IET on more than 100%. + better performance in many cases and has potential for future improvements, like zero-copy + with Linux cache FILEIO. In many tests iSCSI-SCST outperforms tuned for best + performance IET on more than 100%.

    If you are an IET user before installation carefully read README files of both iSCSI-SCST and diff --git a/www/target_qla_isp.html b/www/target_qla_isp.html index f078cf42a..e955ff8c6 100644 --- a/www/target_qla_isp.html +++ b/www/target_qla_isp.html @@ -63,9 +63,10 @@ Stanislaw Gruszka for Open-E Inc.

    This driver operates on the same hardware as the qla2x00t target driver, but, comparing to version 1.0.1.1 - of it, has two notable advantages: support of 24xx (4Gbps) and 25xx (8Gbps) series of QLogic adapters as well - as NPIV support. From other side, qla2x00t is simpler, smaller and much better tested on 22xx and 23xx, hence perform more - reliable and, thus, is recommended for these adapters.

    + of it, has a notable advantage: support of 24xx (4Gbps) and 25xx (8Gbps) series of QLogic adapters. + From other side, qla2x00t is simpler, smaller and much better tested on 22xx and 23xx, hence perform more + reliable and, thus, is recommended for these adapters. (Support of 24xx (4Gbps) and 25xx (8Gbps) + series of QLogic adapters was added in version 2.0.0 of qla2x00t.)

    The latest release is 1.0.1. It does not support 25xx chipsets yet and can be compiled with Linux kernel versions between 2.6.16 and 2.6.27. You can find support for 25xx chipsets and the latter kernels