On Thu, 2006-03-16 at 01:39 +0200, Michael S. Tsirkin wrote: > Quoting Tom Tucker <[EMAIL PROTECTED]>: > > > I think the CMA needs to manage its port spaces. I'm just not sure yet > > > how > > > to do this in a way that works for iWarp yet. And it hasn't been a high > > > enough priority for me to go back and create a patch for it. It sounds > > > like > > > I need to revisit this soon though... > > > > I agree...and I have an idea of how to do it too (see > > inet_csk_get_port). If we could only get this core support in the > > trunk... ;-) > > OK, so if we all agree bind with port 0 will select a free one, > I'll proceed with this assumption and Sean will code up the IB part, > iWarp part won't be a problem when its merged. > Actually, iWARP will need to use this service too. The reason is that most iWARP adapters are also Ethernet interfaces (i.e. "converged NICs"). So in order to be keep the host TCP and iWARP port spaces from clobbering each other, the iWARP side needs to allocate a port via inet_csk_get_port.
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
