On Wednesday 06 December 2006 16:50, Mike Christie wrote: > > For iscsi, we could negotiate a value like MaxBurstLength which says > > don't send commands with a payload larger than that size. I would guess > > other transports have something similar. We have to check or make sure ... > Oh yeah the exception I am thinking about may not be max sectors exactly > but something close like iscsi's MaxBurstLength limit. Maybe iscsi LLDs > are supposed to be translating that iscsi limit to max_sectors in which > case we are talking about the same thing. For this limit we do not want Sort of off topic, but the iSCSI MaxBurstLength doesn't set the max transfer size, it simply is the amount of data that can be sent without a R2T. If the transfer is larger then you have to wait for the R2T. In practice it ends up controlling the _minimum_ amount of buffer space that needs to be available _before_ the transfer starts, otherwise performace sucks. -- PHB REQ: Privileged or confidential information may be contained in this message. If you are not the addressee of this message please notify the sender by return email and thereafter delete the message. You may not use, copy, disclose or rely on the information contained in this message. Internet e-mail may be susceptible to data corruption, interception and unauthorized amendment for which Gresham does not accept liability. While we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Gresham does not accept liability for any damage sustained as a result of viruses. Statements in this message that do not relate to the business of Gresham are neither given nor endorsed by the company or its directors. A list of Gresham's directors is available on our web site: <www.gresham-computing.com> - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
