[stgt] [PATCH 14/15] Fix iSCSI Data-Out solicitation

Arne Redlich arne.redlich at googlemail.com
Tue Jun 23 09:12:29 CEST 2009

Am Dienstag, den 23.06.2009, 16:10 +0900 schrieb FUJITA Tomonori:
> On Tue, 23 Jun 2009 08:57:44 +0200
> Arne Redlich <arne.redlich at googlemail.com> wrote:
> > Am Dienstag, den 23.06.2009, 08:06 +0900 schrieb FUJITA Tomonori:
> > > 
> > > But if an initiator doesn't configure MaxBurstLength, we use the
> > > default value, 256K, which is smaller than what we use now (512K).
> > 
> > Yes, but the target still cannot override it: if an initiator doesn't
> > explicitly propose MaxBurstLength the target must either use the default
> > value from the spec or  explicitly propose another one. The initiator
> > could then agree on that value.
> > 
> > I have no idea if there are implementations that go to this level of
> > complexity (any input welcome!). Though I don't have any data to back
> > that up, my guess would be that initiator implementations will then just
> > reply with the default value anyway.
> Hmm, I think tgt proposes a parameter value if it is different from
> the default in the spec, and open-iscsi can handle it.
> IET can do that too, I think.

Yes, the proposal part at the target works, I just wasn't sure whether
initiators would accept such a proposal or just reply with the default.


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 mailing list