James Lentini wrote:
Our goal is to provide an interface with semantics similar to the sockets interface. A socket's listen function does not block (e.g. inet_listen). Since not blocking is what ULPs expect, kDAPL's listen function does not block. The same should be true of the CMA function.
From what I can see, kDAPL connect and listen calls can block, as does inet_listen. I'm referring to the thread blocking within the call, specifically on a semaphore and memory allocation using GFP_KERNEL. I am not referring to listen blocking until a connection request is received.
- 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
