RE: [PATCH 1/7] libibumad: Provide MAD definitions with libibumad

Hefty, Sean
2013-02-20T16:07:59Z

> > +/* RMPP information */
> > +#define UMAD_RMPP_VERSION 1
> > +enum {
> > + UMAD_RMPP_TYPE_DATA = 1,
> > + UMAD_RMPP_TYPE_ACK = 2,
> > + UMAD_RMPP_TYPE_STOP = 3,
> > + UMAD_RMPP_TYPE_ABORT = 4,
> > +
> > + UMAD_RMPP_FLAG_MASK = 0x07,
> > + UMAD_RMPP_FLAG_ACTIVE = 1,
> > + UMAD_RMPP_FLAG_FIRST = (1 << 1),
> > + UMAD_RMPP_FLAG_LAST = (1 << 2),
> > +
> > + UMAD_RMPP_RESP_TIME_SHIFT = 3,
> > + UMAD_RMPP_NO_RESP_TIME = 0x1F,
> > +
> > + UMAD_RMPP_STATUS_SUCCESS = 0,
> > + UMAD_RMPP_STATUS_RESX = 1,
> > + UMAD_RMPP_STATUS_ABORT_MIN = 118,
> > + UMAD_RMPP_STATUS_T2L = 118,
> > + UMAD_RMPP_STATUS_BAD_LEN = 119,
> > + UMAD_RMPP_STATUS_BAD_SEG = 120,
> > + UMAD_RMPP_STATUS_BADT = 121,
> > + UMAD_RMPP_STATUS_W2S = 122,
> > + UMAD_RMPP_STATUS_S2B = 123,
> > + UMAD_RMPP_STATUS_BAD_STATUS = 124,
> > + UMAD_RMPP_STATUS_UNV = 125,
> > + UMAD_RMPP_STATUS_TMR = 126,
> > + UMAD_RMPP_STATUS_UNSPEC = 127,
> > + UMAD_RMPP_STATUS_ABORT_MAX = 127
> > +};
>
> Should RMPP be included here as it's not currently exposed to user space ?

I need to check the kernel code, but I believe that the RMPP header is exposed.

- Sean