[openib-general] CMA issue: bind selects the same port after close

Michael S. Tsirkin mst at mellanox.co.il
Tue Sep 12 20:57:20 PDT 2006


Quoting r. Tom Tucker <tom at opengridcomputing.com>:
> Subject: Re: [openib-general] CMA issue: bind selects the same port after close
> 
> 
> There is a whole array of Linux port management services that perform
> exactly the logic that you are trying to emulate. Wouldn't our efforts be
> more productively spent figuring out to use the existing services you are
> currently trying to emulate? What do you do, for example, when the port
> allocation policy in the kernel changes? Change your emulation?
> 
> I completely understand that the existing port management services are not
> exported, but functionally, they support multiple port spaces, show up in
> netstat, etc... Can someone please explain to me the reluctance to use these
> services in favor of replicating them?
> 
> Sorry if this reads as a rant...but I feel we're on the wrong track...

Hmm.

inet_csk_get_port actually *is* exported, and while it might be hard for CMA to
use it (needs struct sock*), maybe it is easy for SDP.

So, possibly we should just leave the CMA port allocation as is,
and enhance SDP to use inet_csk_get_port.

-- 
MST




More information about the general mailing list