We also have some management applications which also need these capabilities. For those applications, the use of application RMPP control allows the application to perform some pacing of the RMPP transactions, permits some parts of the RMPP response to be built on the fly and also permits a degree of sharing of the response data between multiple requestors.
-----Original Message----- From: Roland Dreier [mailto:rdre...@cisco.com] Sent: Friday, June 04, 2010 3:54 PM To: Mike Heinz Cc: linux-rdma@vger.kernel.org; Hal Rosenstock; Hefty, Sean Subject: Re: [PATCH v2] allow passthrough of rmpp packets to user mad clients > This patch changes this behavior so that rmpp_version of 255 causes incoming > rmpp packets to be passed through without alteration, instead. > > There are IB users who have requested the ability to perform RMPP > transaction handling in user space. This was an option in old proprietary > stacks and this is useful to migrate old applications to OFED while > containing the scope of their application changes. I'm a little dubious about this. We have an RMPP implementation in the kernel, and it seems worthwhile to focus on stability and features there. Allowing alternate RMPP implementations in userspace seems a bit iffy -- we don't have a socket option that lets us do TCP in userspace for a given connection, for example. -- Roland Dreier <rola...@cisco.com> || For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html -- 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
