[rds-devel] [PATCH] opensm: fix iser service-id used for SL assignment
Jon Mason
jon at opengridcomputing.com
Thu Nov 6 12:23:22 PST 2008
On Thu, Nov 06, 2008 at 10:58:24AM -0800, Andy Grover wrote:
> Or Gerlitz wrote:
> > BTW - while doing this fix, I noted that the port assumed by opensm
> for RDS is 18634
> > (0x48CA) which is the ones used in the rds code deployed in ofed
> > 1.3.x, where the rds code based deployed into ofed 1.4.y uses port
> > 18635
> >
> > Andy, Rick, can you guys revert to 18634 to make things simpler wrt
> > RDS/QoS configuration?
>
> It appears this is a fix for multiple rds transports each trying to bind
> to that port with INADDR_ANY, see commit f0af6566. I think the correct
> fix is to use a single port but have transports listen on their specific
> interfaces only.
>
> I think this is too big a fix for 1.4.0 so I will simply disable TCP
> transport there (leaving just IB transport, thus no problem) and move
> the port back to 18634. For 1.4.1 we will have multiple transports again
> and will need to fix this by not using INADDR_ANY, as described above.
There needs to be a separate port for all the interfaces. IIRC, each
RDS transport type is listening on a specific port for incoming
connections. With each one squatting, the other ones will receive
incoming connections. So for the existing iWARP setup in RDS, they
must be separate.
If they are migrated to a specific physical port or IP address/port
tuple, then this is not an issue. Also, there should be a standard port
to listen on (and not squat on an ephemeral port, as this can cause
problems).
Thanks,
Jon
>
> Regards -- Andy
More information about the rds-devel
mailing list