> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 21, 2007 6:39 PM > > Sorry to be confusing in my last reply, this is an iSCSI > Initiator issue, and is clearly obvious in the following > section of code of code. > > From iscsi_ioctl.c: > case ISCSI_LOGIN_PARAM_MAX_CONNECTIONS: > case ISCSI_LOGIN_PARAM_OUTSTANDING_R2T: > case ISCSI_LOGIN_PARAM_ERROR_RECOVERY_LEVEL: > rtn = ENOTSUP; > break;
OK, well that at least confirms the behavior of the iscsiadm utility. That leads me to the reason I was attempting to change this parameter. I was attempting influence the max command sequence window size discussed in the following entry: http://blogs.sun.com/dweibel/entry/iscsi_kernel_visibilty Is this behavior dynamically managed by the initiator, and if not, how do I affect the size of this window? I am attempting to squeeze the max performance out of iscsi targets exported from thumpers over 10GbE, aggregated in to a zfs pool on T2000s. Thanks, paul _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
