>
> Hi Leon, Steve, all,
>
> >From what I've heard, major checkpoint for siw acceptance
> is rdma netlink integration for dynamic parameter setting.
> Are there already plans & activities for rxe, which would have
> the same obligation? We shall in any case synchronize and make
> it something sound, something where both drivers can
> peacefully co-exist ;)
>
>
> Thanks!
> Bernard.
Hey Bernard,
I think the idea is to extend the 'rdma' command in iproute2 to configure the rxe and siw devices.
The upstream git repo is:
git://kernel.org/pub/linux/utils/net/iproute2/
Currently you can do things like:
[root@stevo1 ~]# /root/stevo/iproute2/rdma/rdma dev
1: mlx4_0: node_type ca fw 2.36.5000 node_guid f452:1403:0027:c4f0 sys_image_guid f452:1403:0027:c4f3
2: cxgb4_0: node_type rnic fw 1.18.2.0 node_guid 0007:4304:b020:0000 sys_image_guid 0007:4304:b020:0000
[root@stevo1 ~]# /root/stevo/iproute2/rdma/rdma link show mlx4_0/1 -d
1/1: mlx4_0/1: state ACTIVE physical_state LINK_UP
caps: <CM, IP_BASED_GIDS>
Maybe to add a network interface to a soft-rdma device like rxe, we could create a syntax like this:
rdma link set rxe_eth0 dev eth0
and to delete it:
rdma link delete rxe_eth0
I'm modeling this off of the 'ip link' command.
Leon, have you thought more about this?
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
