[ofa-general] IPOB CM (NOSRQ) [PATCH V9] patch

[Pradeep Satyanarayana]

Sean Hefty wrote:
>> In the interest of reaching a quick resolution, would it be acceptable
>> if I put
>> in a warning message (printing current memory usage) when memory usage
>> say exceeds 1GB for no srq and also eliminate the max_receive_buffer
>> module parameter. Is that satisfactory?
> 
> That would work for me.  You could even print a warning if the user
> configures ipoib such that it could exceed X GBs.

That brings up questions like how does the user configure ipoib? That means
adding additional parameters. It was felt that 1GB was large enough to flag
it and so I will stick with that.

> 
> That would only leave the max_rc_qp parameter, right?  Is there any
> reason not to rename this to max_conn_qp in case UC support were ever
> added?  Or would we want separate parameters for RC and UC?  (Other
> changes I suggested could easily wait until we have a UC implementation.)

Since we do not know what UC will add to the mix, I would like to keep that
separate.

Pradeep