FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0 2017-11-23T14:28:14Z 2017-11-23T14:28:14Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-23T14:28:14Z urn:sha1:82725ba9bf1fd59746a4006a06f24d4d61d142f2 2017-11-23T13:57:44Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-23T13:57:44Z urn:sha1:9ac7c5a64ca5728ea0ed15fc3c191695938f226d can be used prior to the ISCSIDHANDOFF IOCTL which set the negotiated values. Else the login PDU will fail when passing the "-r" option to "iscsictl" which means iSCSI over RDMA instead of TCP/IP. Discussed with: np@ and trasz@ Sponsored by: Mellanox Technologies MFC after: 1 week 2017-11-23T12:25:11Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-23T12:25:11Z urn:sha1:8d73c9ba61beefc1e69a3871a0875c84bf171819 There is no need to free this mr. This fixes an issue accessing freed memory in ISER. Sponsored by: Mellanox Technologies 2017-11-21T13:56:30Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-21T13:56:30Z urn:sha1:2b378326f89d75b9612cc912f7fa2257cca9a97f else WITNESS will panic. Prefix all mutex names with "iser_" to prevent future WITNESS issues. Sponsored by: Mellanox Technologies MFC after: 1 week 2017-11-16T13:28:00Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-16T13:28:00Z urn:sha1:41dbd9dd1daa87ec7722fc7744236e66581cbc90 Sponsored by: Mellanox Technologies 2016-08-25T05:22:53Z Navdeep Parhar np@FreeBSD.org 2016-08-25T05:22:53Z urn:sha1:97b84d344d4a7bb9e34703948e31be5247318a71 Decouple the send and receive limits on the amount of data in a single iSCSI PDU. MaxRecvDataSegmentLength is declarative, not negotiated, and is direction-specific so there is no reason for both ends to limit themselves to the same min(initiator, target) value in both directions. Allow iSCSI drivers to report their send, receive, first burst, and max burst limits explicitly instead of using hardcoded values or trying to derive all of them from the receive limit (which was the only limit reported by the drivers prior to this change). Display the send and receive limits separately in the userspace iSCSI utilities. Reviewed by: jpaetzel@ (earlier version), trasz@ Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D7279 2016-05-27T11:37:02Z Edward Tomasz Napierala trasz@FreeBSD.org 2016-05-27T11:37:02Z urn:sha1:e199d806842289849035e184c4f73399ad376d45 MFC after: 1 month Sponsored by: The FreeBSD Foundation 2016-05-26T11:40:07Z Edward Tomasz Napierala trasz@FreeBSD.org 2016-05-26T11:40:07Z urn:sha1:4686f1a660ab0a2f37b525fce5b3bfd06dc55027 MFC after: 1 month Sponsored by: The FreeBSD Foundation 2016-05-26T10:30:03Z Edward Tomasz Napierala trasz@FreeBSD.org 2016-05-26T10:30:03Z urn:sha1:95c4a39244184b2df3cb34b842859a57facc284b in ICL interface. - the ordering of parameters to icl_conn_task_setup is different, so that the "cookie" is last. - the icl_conn_connected() method is gone, replaced by much simpler mechanism. I'd rather keep the ICL interface as small as possible. - I don't really like the s/offload/driver/g. The "tcp" is not a driver; "iser" is not really a driver either. I'd prefer to leave it as it is. - the check for ic_session_type_discovery() in iser_conn_handoff() is gone, as handoff cannot happen for discovery sessions. - ic_session_login_phase() and ic_session_type_discovery() are gone. If you had your handoff method called - you're no longer in either of those. - the way maxtags is passed is different; now it's simply ic->ic_maxtags. It's cleaner, and the old way would cause weird things to happen if fail_on_disconnection=1 and the user changed the maxtags sysctl before reconnecting (basically the CAM idea of maxtags would be different from iSER one). - icl_hba_misc() is gone; declare support for PIM_UNMAPPED by setting ic->ic_unmapped flag. - the way we find the "iser" ICL module is rewritten - we have a flag for icl_register() that says if the module is iSER-capable or not. - icl_conn_release() is gone; iser_conn_release() is called from iser_conn_free() (no functional change in this case) and at the beginning of icl_conn_connect(), to handle reconnection. MFC after: 1 month Sponsored by: The FreeBSD Foundation 2016-05-26T09:53:24Z Edward Tomasz Napierala trasz@FreeBSD.org 2016-05-26T09:53:24Z urn:sha1:f83f88912d34013ef23005d36e35d9131a3a59b8 MFC after: 1 month Sponsored by: The FreeBSD Foundation