Good point about the endianness bug. That could be something.
I got 0x600 for status (printed as %x). We have a Topspin switch which runs the SM
Pradeep
[EMAIL PROTECTED]
Roland Dreier <[EMAIL PROTECTED]> wrote on 10/18/2005 11:11:46 AM:
> Pradeep> Now mad_hdr.status field is declared as __be16. So,
> Pradeep> should the check be
>
> Pradeep> (mad_recv_wc->recv_buf.mad->mad_hdr.status & 0xff)
>
> Pradeep> before we return EINVAL?
>
> I don't see why. For one thing, that would be an endianness bug,
> since as you say, the status field is in big-endian order, so the test
> would be different depending on whether the host is big- or little-endian.
>
> Also, all 16 bits of the status field should be zero if the request
> succeeds. What value do you see in the status field in the failed
> response? What SM are you using?
>
> - R.
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
