[stgt] [PATCH 14/15] Fix iSCSI Data-Out solicitation
fujita.tomonori at lab.ntt.co.jp
Fri Jun 19 10:44:34 CEST 2009
On Fri, 19 Jun 2009 10:37:49 +0200
Arne Redlich <arne.redlich at googlemail.com> wrote:
> Am Freitag, den 19.06.2009, 16:54 +0900 schrieb FUJITA Tomonori:
> > On Wed, 17 Jun 2009 08:46:50 +0200
> > Arne Redlich <arne.redlich at googlemail.com> wrote:
> > > 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."
> > In iSER case, the Desired Data Transfer Length MUST not exceed WHAT?
> MaxBurstLength (or the limit incurred by the implementation, i.e. the
> iSER mempool, depends on which is smaller).
Can you tell me where I can find the description about it in RFC 5046?
And can you also tell me where I can find the description about the
length limitation of Data-in in RFC 5046 (your patch uses the max
burst in iSER)?
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt