On Tue, Jun 8, 2010 at 12:27 PM, Hefty, Sean <sean.he...@intel.com> wrote: >> Sean - remember that this patch will still return a BUSY status to the >> caller, if retries are exhausted and the last return code was BUSY, then >> that's what the caller will get. Thus, code which sets retries to zero will >> not be affected by this patch at all. > > It looks like it only returns the BUSY response if that matches with the last > retry, otherwise, the BUSY response is dropped. It also looks like it > applies to all MADs, including vendor specific ones, and not just those from > the SA.
Per the proposed patch, it currently includes trap represses (as determined by ib_response_mad). Shouldn't busy be ignored for that case ? I don't think that would be used but it seems safer to me. -- Hal > > - Sean > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
