> > This patch resolves the issue by allocating a kernel socket consuming > > the TCP port for the iWARP connection upon connection creation and > > freeing the socket once the iWARP connection is destroyed. > > Hasn't this exact approach been explicitly NAK'ed by David Miller?
Yes but this approach still is the simplest and cleanest way to solve this problem that I am aware of. I do want to make clear on the network resource usage. For example, if you run an MPI job over host TCP stack and the job creates 4 connections thus consuming 4 sockets. With this patch, the same job over iWARP will consume 4 sockets. This patch has zero impact on non-iWARP applications and only consumes equal amount of network resources. I would like this patch to be reconsidered for inclusion into the kernel. Chien -- 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
