> For the UDP port used by the usNIC QP, the usnic_verbs kernel driver > requires user space to pass a file descriptor of a regular UDP socket down > at create_qp time. The reference count on this socket is incremented to > make sure that the socket can't disappear out from under us. Then an RX > filter is installed in the NIC which matches UDP/IP/Ethernet packets that > are destined for the UDP port to which the given socket is already bound. > So there is a real UDP socket to make most of the usual things happen in > the net stack, but the raw UDP/IP/Ethernet packets get delivered directly > to the user space queues by the NIC. E.g., "netstat" and "lsof" show you > proper addressing information, though obviously any information related to > data-path statistics will not be accurate. At teardown we just reverse > the steps. > > However, I'm not sure if that's the sort of information you were looking > for.
This is more part of the RoCEv2 discussion than this thread. But, yes, this is what I was looking for. Conceptually, this is loosely similar to the port mapper functionality in iWarp, with a direct port mapping. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
