On Tue, Jul 10, 2007 at 10:11:44AM +0300, Erez Zilber wrote: [...]
> The iSER header issue was discussed in the open-iscsi list: > > http://groups.google.com/group/open-iscsi/browse_thread/thread/23ee18054e8412e6/fd4182f0b141c2da?lnk=gst&q=iSER%2FiWARP+Support+in+version+2.6.20&rnum=1#fd4182f0b141c2da > > For some reason, another answer given by Mike Ko does not appear in this > thread. Here it is: > > For Infiniband, if both the initiator and the target support Zero-Based > Virtual Address, then the iSER header as defined in the IETF draft will > be used. (Zero-based Virtual Address is used in iWARP but optional to > implement in Infiniband.) However, if either the initiator or the target > in an Infiniband environment does not support Zero-Based Virtual > Address, then the expanded iSER header as defined in the Infiniband > annex is used. This expanded iSER header is only used in Infiniband. > There is no intention to provide a link in the IETF draft since this is > purely an Infiniband issue. Ok, so this isn't somthing that I will need to worry a lot about if I am planning on using iWARP? > I hope this helps. It does, thank you. > BTW - do you plan to use the current iSER initiator > code for iWARP? Yes, we are working on an iSER-assisted initiator and target using this code and the UNH iSCSI implementation. Thanks again, Ethan Burns _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
