arne.redlich@xxxxxxxxxxxxxx wrote on Wed, 17 Jun 2009 08:46 +0200: > This wasn't an interpretation as the specs leave absolutely no room for > that, I was just rephrasing them. Here's the verbatim quotes: > > RFC 3720 (iSCSI), 10.8.4 (Desired Data Transfer Length and Buffer > Offset): > "The Desired Data Transfer Length MUST NOT be 0 and MUST not exceed > MaxBurstLength." > > RFC 5046 (iSER), 7.3.6 (Ready To Transfer (R2T)): > "4. [..] To transform the R2T PDU, the iSER layer at the target: [...] > d. MUST use the Desired Data Transfer Length from the R2T PDU as the > RDMA Read Message Size of the RDMA Read Request Message." That's a pretty convincing explanation too! :) Like I said, I can see the merit this way as well. It's the testing that worries me. Which is why I had tried to propose a minimal change that would fix non-RDMA R2T but not change iSER. -- Pete -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
