| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Andy Grover <agrover@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue :
During login negotiation if the MaxRecvDataSegmenLen given by the
target is 0, then MRDSL default value of 8K should be considered.
Some old targets close the CXN if the PDU received size is greater
than the MaxRecvDataSegmentLen set during negotiation.
Fix :
When target is not sending MaxRecvDataSegmentLen in the negotiated
params the value is 0. be2iscsi was setting max_xmit_dlength to 64k
in this case. This fix sets the MaxRecvDataSegmentLen=8k if during
negotiation the MaxRecvDataSegmentLen=0
Signed-off-by: John Soni Jose <sony.john-n@emulex.com>
Signed-off-by: Jayamohan Kallickal <jayamohan.kallickal@emulex.com>
|
| |
|
|
|
| |
be2iscsi hw/fw only supports initial_r2t_en = 1, so
set this in be2iscsi.c.
|
| |
|
|
|
|
| |
If the user has not set MaxXmitDataSegmentLength and
the target sends a value we do not want to set the
value larger than what the driver can support.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This adds a MaxXmitDataSegmentLength param to iscsid.conf.
It will limit the size of the pdu we send to the target.
If you set it to 0, then we use the old behavior where we
just use whatever the target requested. If you set it to
a valid value then we use the min of the set value and
what the target requested.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
|
| |
|
|
| |
This adds some more driver/hw limits for be2iscsi.
|
|
|
This patch adds a be2iscsi template.
be2iscsi needs FirstBurstLength to be 8K or less so this
adds a create_conn callout so it can force negotiation for this
value.
|
