Below's a patch to fix IET's inability of handling separate MaxRxDSLs
for initiator and target.
I didn't touch the kernel module's sanity check of the MaxRxDSLs,
although I feel it's currently too restrictive. If a too large value (>
256k) is configured/announced for the target's/initiator's MaxRxDSL, the
minimum value (512) is chosen, which is IMHO a rather hard punishment.
I'd prefer the target to use the maximum supported value in this case.
Any thoughts on this?
Arne
--
Arne Redlich
Xiranet Communications GmbH
r1247-maxdsl.patch
Description: Text Data
| 