On Thu, May 29, 2008 at 04:11:09PM -0700, Roland Dreier wrote:
>  > Currently, RDS will bind to a single port during bring up of both the IB 
> and TCP
>  > sub-modules.  This binding of 2 different processes to a single port 
> causes a
>  > port space collision to devices which are aware of both (e.g., iWARP).  
> This
>  > prevents iWARP devices from working with RDS if both TCP and IB are 
> compiled in.
> 
> Of course nothing prevents another hapless application from trying to
> use port 18635 with TCP...

Yes, but that potential problem was already there.  I suppose in the long run 
RDS
should try to get IANA to give a reserved port (assuming that the RDS of ports 
1540
and 1541 is a different RDS).

> Not really much we can do about the general port space collision problem
> unless and until the network stack guys are willing to cooperate though.

While I agree it is a necessity, I don't think I want to be the one to start 
that fight
again.  Perhaps if/when RDS is merged with mainline.

>  - R.
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to