[ofw] ndrping issues

Hefty, Sean sean.hefty at intel.com
Tue Jan 5 13:00:14 PST 2010


>No, it's for both active and passive.  The passive side calls it after
>GetConnectionRequest completes, but before calling CreateEndpoint and Accept.

The documentation should be updated to reflect this then:

	GetConnectionData Method

	Retrieves the private data that the peer sends when it accepts
	or rejects the connection request.
	...

	Remarks

	The connecting peer calls this method after the Connect call
	completes and before calling the INDConnector::CompleteConnect method

This reads like it is only for the active side of the connection.  At least for winverbs, the implementation allows either side to call the function.

>The CM will cap the responder resources given in the REP to the limit of the
>HCA already (see __save_user_rep.)  So if GetConnectionData doesn't cap the
>values, the code *could* allow a larger value to be specified and silently cap
>it by using the value the CM stores in the REP.  A bit kludge, though.

I saw that code, but didn't see anything capping the number of reads going from the server to the client, which is the problem in this case.



More information about the ofw mailing list