> I didn't bring it up on the call because I wanted to check on a couple of > semantics, but I think you could just use a single > "socket(AF_UNIX,SOCK_DGRAM,0)" socket per endpoint RX context. This should > scale -- it doesn't blow up as O(P^2) like RC QPs / SOCK_STREAM sockets / > named pipes would. You could expose that UNIX domain socket fd directly to > the libfabric application or you could shove it into an epoll set and then > the app would be given the epoll instance's FD.
Thanks - I was leaning toward SOCK_DGRAM as well, though I hadn't thought of AF_UNIX. - Sean _______________________________________________ ofiwg mailing list [email protected] http://lists.openfabrics.org/mailman/listinfo/ofiwg
