On 04/07/2015 08:49 PM, Hefty, Sean wrote: [snip] >> @@ -515,8 +515,10 @@ ssize_t ib_uverbs_query_port(struct ib_uverbs_file >> *file, >> resp.active_width = attr.active_width; >> resp.active_speed = attr.active_speed; >> resp.phys_state = attr.phys_state; >> - resp.link_layer = rdma_port_get_link_layer(file->device- >>> ib_dev, >> - cmd.port_num); >> + resp.link_layer = rdma_transport_ib(file->device->ib_dev, >> + cmd.port_num) ? >> + IB_LINK_LAYER_INFINIBAND : >> + IB_LINK_LAYER_ETHERNET; >> >> if (copy_to_user((void __user *) (unsigned long) cmd.response, >> &resp, sizeof resp)) > > Both of the above check the transport in order to determine the link layer. > > These values are exposed to user space. Does anyone know what link layer iWarp returns to user space? It should be ETH for IWARP according to the old logical :-) Regards, Michael Wang > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
