Subject: RE: [Ips] iSCSI: intent of MaxCmdSN

From: [email-masked]
Date: Tue, 10 Feb 2004 11:41:26 -0700

Eddy,

Your view seems to assume that iSCSI only has to worry about queuing for reordering out of order command arrivals. Even if MaxCmdSN isn't used to regulate flow to the SCSI layer, iSCSI still has an interest in the command after it has passed it to SCSI.

There are iSCSI resources tied up in a command until the status has been received (initiator) or the status has been acknowledged (target). MaxCmdSN is a way to regulate the demand on those resources throughout the life of the command.

Pat

"Eddy Quicksall" <[email-masked]> 
Sent by: [email-masked]
09/02/2004 10:23

To
<[email-masked]>
cc

Subject
[Ips] iSCSI: intent of MaxCmdSN

Regarding MaxCmdSN, is the intent to regulate the flow of commands to the 
SCSI layer or to regulate the flow to iSCSI for multiple connections?
 
It seems that it must be for multiple connections to reduce the number of 
commands that are waiting to be ordered to SCSI. And that the SCSI layer 
should be responsible for its own queue depth.
 
But, I just wanted to see if I'm missing something.
 
Eddy

_______________________________________________
Ips mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ips