Re: Data in SCSI Response or SCSI Data

[julian_satran@il.ibm.com]

Any software implemementation will have 2 reads/iSCSI message.
As we asume a large number of software implementations being used as
initiators having the double the number of reads for small I/O is not wise.
Hardware will easily manage the different read modes.

Julo

csapuntz@cisco.com on 25/08/2000 01:38:24

Please respond to csapuntz@cisco.com

To:   "'ips@ece.cmu.edu'" <ips@ece.cmu.edu>
cc:   csapuntz@cisco.com (bcc: Julian Satran/Haifa/IBM)
Subject:  Re: Data in SCSI Response or SCSI Data





If I remember the discussion correctly, I remember some folks who
were implementing hardware did not like having 3 different
mechanisms for doing the same thing, as this required more logic
and verification.

From a network performance standpoint, there is minimal difference
between sending two iSCSI messages back-to-back and one larger
iSCSI message.

In fact, both iSCSI messages might even share the same packet.

-Costa

Matthew Jacob <mjacob@feral.com> writes:

> > > *   Data and status sent in a SCSI Response packet
> >
> > I think the plan is to remove these last two approaches in the next
> > edition of the spec.
>
> Why? There are a lot of 'trivial' commands that could be done with one
packet.
>
> -matt