Ping, anyone had a chance to look over this one? Cheers, Dave
On Wed, 26 Nov 2008 16:19:22 +1100 David Disseldorp <[EMAIL PROTECTED]> wrote: > iSCSI/iSER targets may send PDUs without a prior request from the initiator, > RFC 5046 refers to these PDUs as "unexpected". NOP-In PDUs with itt=RESERVED > and Asynchronous Message PDUs occupy this category. > > The amount of active "unexpected" PDU's an iSER target may have at any time is > governed by the MaxOutstandingUnexpectedPDUs key, which is not yet supported. > > Currently when an iSER target sends an "unexpected" PDU, the initiators recv > buffer consumed by the PDU is not replaced. If over initial_post_recv_bufs_num > "unexpected" PDUs are received then the receive queue will run out of receive > work requests. > > This patch ensures recv buffers consumed by "unexpected" PDUs are replaced > in the next iser_post_receive_control() call. > > Version 2: > o replace unexpected recv bufs in iser_post_receive_control, transparent > to iser_send_* functions. _______________________________________________ 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
