Files
scst/iscsi-scst/ChangeLog
Vladislav Bolkhovitin 0fd9c9b385 - Version changed to 1.0.0
- Build configuration changed to "Release"
 - iscsi-scst-howto.txt added
 - ChangeLog's updated
 - Minor docs changes
 - scstadm_install and scstadm_uninstall main Makefile targets added



git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@433 d57e44dd-8a1f-0410-8b47-8ef2f437770f
2008-07-07 18:00:32 +00:00

47 lines
1.8 KiB
Plaintext

Summary of changes in iSCSI-SCST since it was IET
-------------------------------------------------
- Commands processing flow changed to work with SCST. Significant
cleanup was done. Modules and config files were renamed to allow to
run with IET on the same host.
- In IET the iSCSI negotiation isn't fully iSCSI RFC confirmed: it doesn't
support ranges of values and, more important, violates RFC in case
when in the IET config file some value for some parameter is set and
a remote initiator doesn't initiate the negotiation for this
parameter or declare its value. According to RFC, in this case IET
shall use the RFC-specified default value, but it uses config file
specified one instead. Looks like the implementation confuses IET
config file default values and iSCSI RFC ones. The default values
handling was fixed. But support for ranges remains unfixed (see ToDo
file).
- All shutdown/restart problems (resource leaks, hangups, etc.), especially
under load, were fixed.
- Full duplex network IO implemented.
- Threading model reimplemented.
- Digests calculation made multi-threaded.
- TX data digest errors handling iSCSI RFC violation was fixed. Another one
(SNACK handling) remains unfixed.
- Ability to send data with sense in a single response added.
- Ability to handle initiators misbehavior a bit improved: several BUG()'s
were relaced by the proper handling. Hovewer, there is a plenty of work in
this area left, IET is known to have a lot of weaknesses here.
- Task management made more robust. Particularly, possible data
corruption scenarios were fixed.
- Implemented SN based iSCSI IO flow control
- Response data send timeout implemented: now if initiator doesn't
accept data for too long (30 sec), target closes connection
- A lot of other bugfixes and code cleanups.