[rds-devel] TCP branch issue (was: new branch future/20090428 available)

Andy Grover andy.grover at oracle.com
Mon Jul 13 17:19:17 PDT 2009


Hi Aaron,

Please try a branch I just pushed -- it's the same repo, on branch
future/20090713.

I just got back from vacation so my memory's a little rusty, but I know
the above branch works for me, and if it doesn't for you, it's a better
starting point to debug from than 0428.

Regards -- Andy

aafabbri wrote:
> I tried building this RDS branch with TCP support, but am running into
> issues.
> 
> [root at savbu-lle-hp-dl160-23 ~]# rds-info
> rds-generic-tool: Unable to create socket: Address family not supported by
> protocol
> [root at savbu-lle-hp-dl160-23 ~]# modprobe rds
> [root at savbu-lle-hp-dl160-23 ~]# rds-info
> rds-generic-tool: Unable get statistics: Protocol not available
> 
> I should have your latest (but maybe not the correct) rds-tools, and built
> my kernel/modules with RDS_DEBUG enabled.  All I see in the syslog is:
> 
> kernel: NET: Registered protocol family 28
> 
> Strace on the last rds-info command (after loading module) looks like this:
> 
> socket(0x1c /* PF_??? */, SOCK_SEQPACKET, 0) = 3
> open("/proc/sys/net/rds/sol_rds", O_RDONLY) = 4
> read(4, "272\n", 4096)                  = 4
> read(4, "", 4092)                       = 0
> close(4)                                = 0
> getsockopt(3, 0x110 /* SOL_??? */, 10008, 0, 0x7fff9e35fb6c) = -1
> ENOPROTOOPT (Protocol not available)
> write(2, "rds-generic-tool: Unable get sta"..., 64rds-generic-tool: Unable
> get statistics: Protocol not available
> ) = 64
> exit_group(1)   
> 
> 
> Now, looking through the code, this seems to imply that
> rds_info_register_func(RDS_INFO_IB_CONNECTIONS) was never called.. And thus
> rds_info_getsockopt() is returning ENOPROTOOPT.  I do not have any IB
> interfaces on this machine.
> 
> Can you help point me in the right direction to get this working?
> 
> Thanks,
> 
> Aaron
> 
> Andy Grover wrote on Tue Apr 28 17:37:45 PDT 2009:
>> Hi all,
>>
>> I've been working on bringing TCP support back, and also demand-loading
>> transport modules. I've pushed what I have so far to:
>>
>> git://git.openfabrics.org/~agrover/ofed_1_4/linux-2.6 future/20090428
>>
>>      RDS: Add back TCP transport support
>>      RDS: Integrate TCP into build process
>>      RDS: Build TCP and RDMA transports as separate modules
>>      RDS: Use request_module() to load transports as needed
>>      RDS: Fix ofed_scripts for new rds config options
>>      RDS/TCP: Shutdown/free all alloced conns on module exit
>>      RDS/TCP: Shutdown sock in rds_tcp_conn_shutdown()
>>      RDS/TCP: Transition to connecting in tcp_connect
>>      RDS: Prevent deadlock on transport autoload
>>
>>
>> Regards -- Andy
> 
> 
> _______________________________________________
> rds-devel mailing list
> rds-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/rds-devel




More information about the rds-devel mailing list