On 2/20/2013 11:39 AM, Hal Rosenstock wrote: > On 2/20/2013 11:29 AM, Hefty, Sean wrote: >>> I need to check the kernel code, but I believe that the RMPP header is >>> exposed. >> >> I looked at copy_recv_mad(), and it copies the entire 256-byte MAD to user >> space, which includes any RMPP header, followed by any additional segmented >> data. So most of the RMPP definitions are relevant, the exceptions possibly >> being UMAD_RMPP_TYPE_[ACK | STOP | ABORT]. IMO - I would keep those for >> completeness. > > Yes but how much of header is relevant when it's a multipacket RMPP MAD > message ? My concern is that it may be confusing as to validity/use of > certain RMPP fields, etc.
How about moving ahead without these for now ? They can always be added back in when the time is right. If that's acceptable to you, I'll make that modification myself and move onto the other libibumad patches in your series. -- Hal > > -- Hal > >> - Sean >> > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
