viswanath krishnamurthy wrote:
Probably called from a callback.. The application
is small application which accepts incoming
connections (Like a socket server).
When is the good time to call the destroy ?
You need to call ib_cm_event_put() after processing a CM event. You can call
ib_cm_destroy_id() anytime, but the call will block if there is an outstanding
event. So, if you're calling it in the same thread that calls
ib_cm_event_put(), it must be done after making that call.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208648784 (LWP 21309)]
0xb7f79de8 in mthca_free_db (db_tab=0x805c688,
type=MTHCA_DB_TYPE_CQ_SET_CI, db_index=494) at
src/memfree.c:150
I'll let Roland respond to this. (Since if he's read the mail, he may already
be working on a fix.)
3. Kernel oops when lots of traffic between
multiple
clients and server. Very consistently
reproducible. See attachment for details
I've run with thousands of connections without any issues. We'll need to spend
some time looking at this to see what the issue might be.
If an HCA has multiple ports, the node guid will be
the
same. It will be good to get the port guid to uniqely
identify the port.
The CM REQ returns the device along with the port number that the REQ was
received on, which can be used to identify the port.
- Sean
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
