To return the error on the active side that "this iWARP device doesn't support IPv6", the following places are the possibility -rdma_connect() -rdma_resolve_addr() -qp setup time rdma_resolve_addr() would probably be the earliest to handle this. For the driver to expose this lack of capability so that rdma_resolve_addr can figure out, we have the following structures available at the rdma_resolve_addr time -ib_device (pointed to by cma_device) -iw_cm_verbs (pointed to by ib_device) -net_device If we don’t want to touch net_device and if this information can be made available through ib_device it might be simpler. If the IB devices won't need to differentiate between the availability of IPv4 and IPv6 capability and only iWARP devices might require it, then Roland was suggesting iw_cm_verbs might be one path out. Seeking suggestions. Thanks! Venkat
________________________________ From: Venkat Venkatsubra <[email protected]> To: Roland Dreier <[email protected]>; Aleksey Senin <[email protected]> Cc: Olga Shern <[email protected]>; "[email protected]" <[email protected]> Sent: Tuesday, December 30, 2008 10:24:35 AM Subject: Re: [ofa-general] [RDMA CM IPv6 PATCHv7 2/2] RDMA CM I had couple of questions regarding RDMA CM supporting IPv6. When an iWARP NIC doesn't support IPv6, what is the earliest an error could be returned saying feature unsupported ? Any time sooner than rdma_connect() for the active connect side ? And what about the passive side ? Venkat
_______________________________________________ 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
